qui_list_cross_instance_torrents

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

The annotation readOnlyHint=true is consistent with the GET method, but the description adds no further behavioral traits. It does not disclose pagination, result aggregation, side effects, or other contextual behavior that an agent would need to know.

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 that conveys the endpoint and argument structure with no redundant words. It is efficient and easy to parse.

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 tool's apparent role as a listing endpoint, the description is incomplete. It does not explain what 'cross-instance torrents' means, when to use it, or what the response contains — the output schema may cover return values, but the description fails to provide the core context needed for tool selection.

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?

The schema is a generic 'arguments' object with 0% description coverage. The description compensates by explaining that path variables go in arguments directly, query values in arguments.params, and body in arguments.body. This provides a useful structural template, though it omits endpoint-specific parameter names and meanings.

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 only states 'Call qui's GET /torrents/cross-instance endpoint,' which restates the tool name with an HTTP method and path. It lacks a clear domain action verb like 'list' or 'retrieve' and does not specify what the tool does or returns, relying entirely on the name for meaning.

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 is given on when to use this tool versus alternatives. There are no use-case descriptions, prerequisites, or exclusions mentioned. The only usage instruction is about argument structure, not tool selection.

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