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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds value beyond annotations by specifying the nature of the returned data (fields, sample data, instructions, LaTeX source) and the directive to read instructions before data collection. It does not contradict annotations and provides useful behavioral context for a read-only fetch.

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 with zero waste. The main purpose is front-loaded, followed by concise routing guidance. Every clause earns its place, and there is no redundant or verbose phrasing.

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?

Even without an output schema, the description names the return components (fields, sample data, filling instructions, LaTeX source) and offers clear next-step actions. It covers the core behavior adequately for a simple fetch tool, though it does not explicitly describe response formatting or error handling. Given the simplicity and the annotations covering safety, this is a minor gap.

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%, and the schema description for the 'template' parameter already specifies it is a slug from list_public_templates with an example. The tool description adds no new parameter information beyond what the schema provides, so the baseline 3 is appropriate.

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 verb ('Get') and resource ('a public template') and enumerates the exact content returned: fields (JSON schema), sample data, filling instructions, and LaTeX source. It clearly differentiates from siblings by naming render_public_template (for making the PDF) and compile (for changing layout), so an agent can distinguish this fetch operation immediately.

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 explicit routing: after fetching, pass data to render_public_template to make a PDF, or edit source and use compile to change layout. It also tells the agent to read the instructions before collecting data from the user, providing clear context for when this tool is the right step in a workflow. Alternatives are named with their conditions, leaving no ambiguity.

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