rvtdocs_fetch

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

With no annotations, the description must fully disclose behavior. It explains output shaping (snippet removal/inclusion) and diagnostics metadata, but lacks information about idempotency, error handling, auth requirements, or side effects. Missing details on whether the tool is read-only or destructive.

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 very short and front-loaded, with bullet points for mode options. However, it is under-specified for a 4-parameter tool; crucial parameter descriptions are missing, making it less effective than it could be at an appropriate length.

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 no output schema, no annotations, and 4 undocumented parameters, the description is incomplete. It only addresses mode selection; the query, year, max_chars, and response format are not described, leaving significant gaps for the agent to infer.

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 0%, so description must compensate. It only explains the 'mode' parameter's options. The 'query', 'year', and 'max_chars' parameters are left entirely undocumented, leaving the agent guessing their meaning and constraints.

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 'Fetch RVTDocs in single-fetch mode', identifying the verb and resource. It implies a distinction from batch operations but does not explicitly differentiate from siblings like rvtdocs_batch or rvtdocs_scan.

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 only provides guidance on selecting the 'mode' parameter (trust vs full vs diagnostics). It does not advise when to use this tool over siblings (e.g., batch vs single fetch) or mention prerequisites or context.

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