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

Discloses the important version-selection behavior: returns the published version if any, otherwise the latest. Annotations already cover read-only/idempotent safety, and the description adds meaningful retrieval semantics without contradicting them.

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 redundant wording. Key distinctions and version behavior are front-loaded and easy to parse.

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?

Covers the core purpose, the version behavior, and the alternative for older versions. Since output schema is present and annotations cover safety, the description is sufficient for correct use, though it could mention that at least one of slug or template_id should be supplied.

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 schema already describes both parameters and their mutual exclusivity ('provide this or template_id'). The description adds little beyond the schema, but the version-selection behavior gives some extra context for how the selected template is resolved.

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?

States a specific verb ('get') and resource ('api template'), and clarifies it returns a single template with its current definition body. It distinguishes itself from get_api_template_version for older versions and from list_api_templates by the word 'single'.

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?

Explicitly directs users to get_api_template_version for reading a specific older version, which is a clear when-to-use alternative. It does not explicitly mention list_api_templates for listing, but 'single' plus 'current version' makes the primary use case unambiguous.

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