laddro.coverLetters.list

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

The description adds the pagination feature beyond annotations (which provide readOnlyHint). However, it does not disclose other behavioral traits like default limits, rate limits, or performance characteristics.

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?

A single sentence of 10 words effectively conveys the tool's purpose and key feature (pagination). No redundant wording.

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?

For a straightforward list tool with an output schema (present), the description sufficiently covers its function: listing the user's cover letters with pagination. Siblings are similar, but no critical details are missing.

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 coverage is 100% with descriptions for both parameters. The tool description does not add new semantic meaning beyond what the schema already provides, aligning with the baseline score of 3.

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 clearly states the verb 'list' and the resource 'authenticated user's cover letters', with 'pagination support' adding scope differentiation. References to pagination distinguish this tool from siblings like 'get' (single item) or 'create'.

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?

The description implies use for listing cover letters but lacks explicit guidance on when to use this tool versus alternatives like 'laddro.resumes.list'. No when-not-to-use or exclusion criteria are provided.

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