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

Annotations already mark this as non-read-only and open-world, and the description adds useful behavioral context: missing fields return a list of what to ask for and cost nothing, and the tool works without an API key within a daily free limit. It does not detail side effects, but the added context goes meaningfully beyond the annotations.

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 main action is front-loaded, and each of the four sentences adds a distinct operational fact: schema matching, missing-field behavior, template interchangeability, and authentication/rate-limit context. There is no filler or 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?

With no output schema, the description still names the return value (a PDF link) and covers the common failure mode (missing fields). It could mention how to discover valid slugs or handle invalid template slugs, but for a two-parameter tool this 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% for both parameters, and the description enriches them: 'data' must match the template schema with defined missing-field behavior, and 'template' is a slug that can be swapped to switch styles. This is useful semantics beyond the generic schema wording.

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 states a specific action and outcome: 'Fill a public template with the user's data and return a PDF link.' It clearly identifies the resource and intended result. However, it does not explicitly differentiate this tool from the sibling 'compile', so some distinction is left to inference.

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 gives concrete usage context: consult get_public_template for the schema, expect a missing-field prompt list, and reuse the same call with a different slug to switch resume styles. It does not explicitly state when to prefer compile or list_public_templates, so exclusions are absent.

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