rvtdocs_batch

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

Without annotations, the description carries the behavioral burden. It mentions two modes ('trust' vs 'full') and the return shape (list of results, aggregate stats). However, it does not disclose potential side effects, authentication needs, or limits, leaving moderate gaps.

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 relatively concise, front-loading the purpose and using a bullet-like list for mode options. It avoids unnecessary verbosity, though the line breaks could be tightened for even greater efficiency.

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 lack of output schema and 4 parameters, the description is incomplete. It does not fully explain return values (beyond vague 'list of results'), error handling, or parameter details like query format. Essential context for effective use is missing.

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%, so the description must compensate. It explains the 'mode' parameter and implies the output structure, but does not describe the format of query strings or the 'year' and 'max_chars' parameters beyond defaults. Partial coverage, but adds some meaning.

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 'Batch-fetch multiple RVTDocs queries in a single tool call,' providing a specific verb and resource. It distinguishes from the sibling rvtdocs_fetch by emphasizing batching, though it could be more precise about what constitutes a 'query.'

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 hints at when to use (reducing overhead for related APIs) but does not explicitly state when not to use or name alternatives. There is implicit context from the sibling list, but no direct exclusion or comparative guidance.

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