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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description contributes nothing beyond that – no note on what the template contains, whether it is a stock or custom template, or any access constraints – so there is no added behavioral value.

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?

It is a single front-loaded sentence with zero waste, but the brevity comes at the cost of under-specification rather than efficiency; there is room for one clause on sourcing templateId or the list/get relationship.

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?

The tool is simple (one param, output schema present so return values need not be described), but with 0% schema coverage the description should at least say what templateId identifies and how to obtain it. Nothing an agent needs to invoke this correctly is stated.

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 0% and the single templateId parameter carries only a regex pattern and length bounds, with no prose description. The tool description never mentions templateId or where a valid value comes from, so it does not compensate for the schema gap.

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?

"Read a PDF export template" names a verb and resource, and the singular phrasing plus required templateId implies a single-record fetch rather than a listing. However it never distinguishes itself from list_export_templates (the obvious way to discover a templateId) or from the many export_* tools in the sibling set.

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?

There is no guidance on when to call this versus list_export_templates, nor any prerequisite such as 'templateId comes from list_export_templates'. The agent must infer the workflow entirely.

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