Describe one provider-qualified exact template

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description doesn't need to restate those. It does add the behavioral constraint that a bare templateId is deliberately insufficient, but it doesn't describe errors, output shape, or any other runtime behavior.

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?

Two concise sentences with no filler. The core constraint ('bare templateId is deliberately insufficient') is front-loaded and directly actionable.

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?

For a read-only describe operation, the description covers the key selection constraint and template categories. The main omission is the exactSelector object schema, but the tool has no output schema and the annotation suite already covers the operational safety profile.

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%, so the description carries the burden. It partially compensates by explaining that providerId plus an exactSelector are required and by listing what kinds of exact selectors are valid. However, the internal structure of exactSelector is left unspecified, which is a meaningful 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?

Clearly states the tool describes an exact provider-qualified template, and enumerates the accepted template categories: Local Published release, bundled/personal public template, or commit-pinned FigureYa module. This differentiates it from generic open/search tools by emphasizing exactness.

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 clear usage context: only exact, provider-qualified selectors are acceptable, and a bare templateId is explicitly insufficient. It doesn't name sibling alternatives, but it effectively rules out the wrong way to call the tool.

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