list_problem_torrents

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

The annotations already disclose readOnly, idempotent, and non-destructive behavior, so the description does not repeat that. It adds filtering scope, but provides no extra behavioral context such as pagination, ordering, or result size details beyond the schema's default limit.

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 description is a single, front-loaded sentence with no filler. It conveys the action and the precise inclusion criteria efficiently, making it easy for an agent to parse quickly.

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 low-complexity, read-only tool with no required parameters, an output schema, and clear annotations, the description is nearly complete. The main omission is guidance on the limit parameter, but the schema default and output schema mitigate the impact.

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%, and the description says nothing about the 'limit' parameter. The parameter name and default value suggest the basic meaning, but the description does not clarify how limiting behaves, such as whether results are truncated or how a custom limit affects the response.

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, 'List', and identifies a distinct resource: problem torrents, explicitly naming the statuses included (missing, errored, unknown, or incomplete stalled/stopped). This clearly differentiates it from the generic sibling 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?

The wording implies this tool is for finding torrents in problematic states, especially stalled or stopped ones, rather than for general listing. However, it does not explicitly mention sibling alternatives or state conditions for when this tool should not be used.

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