get_template

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds almost nothing beyond that: 'original' and 'precise media capabilities' are unexplained and do not clarify what is returned or what 'media capabilities' entails.

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?

A single short sentence with no wasted words; it is appropriately sized and front-loaded. The terseness is a virtue for length, though the content itself is thin.

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?

There is no output schema, one undocumented required parameter, and annotations only cover safety. The description does not explain what the returned 'template' or 'media capabilities' contain, leaving an agent unable to predict the response shape for this lookup tool.

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?

The single 'id' parameter has 0% schema description coverage and the description never mentions it, so an agent learns nothing about what the id refers to (template identifier, slug, etc.). With 1 undocumented parameter, the low-coverage baseline applies and the description fails to compensate.

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 verb+resource (Get ... template) is clear and the word 'one' hints at a single-item fetch, distinguishing it loosely from search_templates and compare_templates. However, 'original template' and 'precise media capabilities' are vague modifiers that leave an agent unsure whether this retrieves template metadata, assets, or generated media specs.

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 statement of when to use this tool versus siblings like search_templates, get_template_source, or verify_template_source. No context about prerequisites or when an agent should prefer this over the other template-related tools is provided.

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