persons.list

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

No annotations provided, so description carries full burden. It does not disclose read-only safety, pagination behavior (despite having cursor parameters startsAfter/limit), rate limits, or permission requirements.

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?

Single sentence with no wasted words and front-loaded information, but under-specification for a 4-parameter tool with complex pagination makes it insufficient rather than appropriately concise.

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?

With 4 undocumented parameters, no output schema, and no annotations, the description should explain the cursor-based pagination pattern and resource semantics, but leaves critical operational gaps.

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?

Schema description coverage is 0%. While 'for an account' hints at the required accountId parameter, the description completely ignores the pagination parameters (limit, startsAfter) and sorting flag (ascending), offering no syntax or semantic guidance beyond the schema names.

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?

The description states a clear verb (List) and resource (Ryft persons) with scope (for an account), but fails to distinguish from siblings like persons.get (which retrieves a single person) or clarify what distinguishes a 'person' from a 'customer' in this API context.

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 listing tool versus persons.get for individual retrieval, nor any mention of when pagination parameters are required or recommended.

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