render_template

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

With no annotations, the description carries full burden. It discloses core behavior (PDF generation from template + data) but omits critical details: return value (binary, file path?), side effects (file storage), error handling, rate limits, or auth requirements. Some transparency is provided but significant gaps remain.

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 two sentences (~40 words) with a clear front-loaded purpose statement. Every sentence serves a purpose: first defines the tool, second provides actionable guidance. No superfluous content.

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?

Despite 9 parameters and no output schema, the description does not explain the return value or behavior (e.g., does it return a PDF binary or store a file?). It also fails to clarify how this differs from sibling `render_template_preview`. Important gaps make it incomplete for a complex tool.

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 baseline is 3. The description adds value by linking to `list_templates` for template discovery and `get_template` for schema details, contextualizing parameters beyond their schema descriptions. This meta-information enhances understanding.

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 generates a PDF from a template using structured data, identifying verb, resource, and mechanism. However, it does not differentiate from sibling tools like `render` or `render_template_preview`, leaving ambiguity about when to use this specific tool.

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 advises using `list_templates` and `get_template` as prerequisites but does not provide guidance on when to use this tool versus siblings (e.g., `render` or `render_template_preview`). Usage context is implied but lacks explicit exclusions or alternatives.

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