recent_series

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

The description mentions 'cover letters' but the tool name is 'recent_series', which may confuse. It explains collapse_revisions behavior but lacks details on ordering, recency criteria, and pagination despite having a limit parameter.

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?

Two sentences with no fluff, concise and to the point. Could be slightly more structured (e.g., separating purpose from collapse_revisions behavior), but efficient overall.

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 4 parameters and an output schema, the description lacks details on what is returned (cover letters vs series), ordering, pagination behavior, and response structure beyond what the schema provides. Incomplete for agent decision-making.

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 75% (three of four parameters have descriptions). The description adds value by explaining collapse_revisions beyond its schema description, but does not explain the limit parameter, which has no schema description.

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 'List recent cover letters on a project', specifying verb, resource, and optional filter. However, it does not differentiate from sibling tools like get_series or search_patches.

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 on when to use this tool vs alternatives. For example, it does not mention that get_series is for a specific series or that search_patches is for broader searches.

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