template_render

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It only mentions features (German helpers, $0.01 cost) but does not disclose side effects, whether it writes to output_path, error behavior, or return format. For a tool with a mutation-like output, this is a significant gap.

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 a single sentence, front-loaded with the core purpose, and includes a compact list of output formats and a cost note. Every phrase adds value with no redundancy.

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 tool has 5 parameters, no output schema, and no annotations, the description is insufficient. It covers the main action and formats but omits critical operational details such as how output_path is used, the role of idempotency_key, error handling, and what the tool returns. An agent would need to guess at several behavioral aspects.

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 only 20% (only 'template' has a description). The description adds meaning to 'data' (JSON data) and 'format' (PDF, PNG, HTML), but leaves 'output_path' and 'idempotency_key' unexplained. It partially compensates for the low schema coverage but not fully.

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 specific action (render a Handlebars template with JSON data) and the output formats (PDF, PNG, HTML), with concrete use cases (invoices, reports, certificates). It distinguishes itself from the sibling 'render' tool by explicitly naming the Handlebars and JSON inputs, leaving no ambiguity about what it does.

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?

It provides context on typical use cases (invoices, reports, certificates) and mentions German helpers, but does not explicitly state when to prefer this tool over alternatives like the generic 'render' sibling, nor any exclusions. The guidance is implied rather than explicit.

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