render_audit_pdf

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

No annotations are provided, so the description must carry the burden. It states it renders a PDF but does not disclose whether it is a pure read operation (no side effects), what happens on conflict (overwrite?), or any rate limits. The phrase 'pass through unchanged' is helpful but insufficient.

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 sentences: first sentence states the purpose, second provides essential input guidance. No wasted words. Perfectly front-loaded and efficient.

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, the description explains the output (PDF file) and default path. It does not mention error handling or prerequisites, but for a simple render tool with clear inputs, it is reasonably complete. Could be improved by noting that all required inputs must be present.

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 input schema has 67% coverage (descriptions for 4 of 6 parameters). The description adds value by indicating that ahrefs/crawl should be passed exactly as returned, that ai_visibility comes from web search, and that narratives are user-written. This clarifies data provenance beyond schema.

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 the tool's purpose: 'Render the completed SEO/AEO audit report as a PDF file.' It specifies the exact resources (ahrefs, crawl, ai_visibility, narratives) and their required form, effectively distinguishing it from sibling fetch tools.

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 explicitly tells the agent to pass through ahrefs/crawl from fetch_audit_data, ai_visibility from web search, and narratives written by the agent. It implies usage after data collection, though it could be clearer about what to do if data is missing.

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