customers.list

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With zero annotations provided, the description carries the full disclosure burden. While 'List' implies a read-only operation, the description fails to explain pagination behavior (cursor vs offset), filtering logic (partial vs exact match on email), or return value structure despite having six behavioral parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

At three words, the description is brief but significantly undersized for the tool's complexity. The single sentence does not earn its place as it merely restates the tool name pattern without adding operational context required for six undocumented parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given six parameters with no schema descriptions, no annotations, and no output schema, the description is inadequate. It fails to explain the pagination mechanism (limit/startsAfter), timestamp filtering boundaries, or sorting behavior that agents need to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 0% description coverage across six parameters (email, timestamps, pagination controls). The description mentions none of these parameters nor explains their semantics, leaving critical filtering and pagination capabilities completely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description states a clear verb ('List') and resource ('Ryft customers'), distinguishing it from sibling operations like 'get', 'create', or 'delete'. However, it does not explicitly differentiate from 'customers.listPaymentMethods' or clarify scope beyond the resource name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance provided on when to use this versus 'customers.get' for retrieving specific records, or how to effectively use the filtering capabilities. The description stands alone without contextual workflow guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.