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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds valuable context beyond them: rate limits (5 calls/hour per IP), payload size cap (8 KB args), pricing via x402, and that output includes per-tool issues and bundles.

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?

Two dense sentences, front-loaded with the tool's purpose and scope, followed by essential operational constraints. No filler; every clause carries information an agent needs.

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 batch conversion tool with annotated safety, full schema coverage, and no output schema, the description covers batch size, output shape (issues/bundles), throughput limits, and cost. It could say more about failure/partial-success behavior, but is largely sufficient.

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 100%, so both parameters are already documented, including the 1-50 item range for tools and the target enum/default for formats. The description adds a useful 8 KB argument-size constraint, but it does not further explain parameter behavior or formatting.

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?

States a specific verb and resource (convert tool definitions), quantifies the batch limit (up to 50), and mentions outputs (per-tool issues, ready-to-use bundles). It implicitly distinguishes itself from the singular convert_tool_schema via batch scope, though it doesn't explicitly name that sibling.

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?

Usage is only implied by the batch framing (up to 50 tools). There is no explicit guidance on when to use this versus convert_tool_schema, lint_tool_schema, or openapi_to_tools, nor any stated exclusions or prerequisites.

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