analyze_largest_torrents

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

Annotations already communicate read-only, idempotent, and non-destructive behavior. The description adds useful selection semantics (size-based ordering and the inactivity-age filter) but does not disclose details such as how results are capped or ordered beyond the word 'largest'.

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?

The entire description is one front-loaded sentence with no filler. Every phrase contributes either the core behavior or the optional filter.

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 the simple two-parameter schema, the presence of an output schema, and annotations that cover safety/idempotency, the description covers the essential behavior. It is only missing explicit sibling differentiation and a more concrete statement of the limit parameter's effect.

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?

With 0% schema description coverage, the description must compensate, and it does clarify inactive_days as a 'minimum inactivity age'. However, the limit parameter is not explained; its meaning is only implied by the word 'largest' and the schema's default of 20.

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 uses a specific verb and resource: 'Return the largest torrents', with an optional inactivity-age filter. It uniquely identifies the tool's role among siblings through the 'largest' qualifier, though it does not explicitly contrast it with list_torrents.

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 when-to-use or when-not-to-use guidance is provided, and no alternatives are named. An agent is left to infer that this should be chosen over list_torrents or list_problem_torrents based solely on the phrase 'largest torrents'.

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