get_template_version

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

Clearly declares 'Read-only' indicating no side effects, and specifies exact fields returned (subject, HTML, plain text, active state). With no annotations provided, this provides good behavioral insight, though could mention error handling.

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?

Single, well-front-loaded sentence that conveys all essential information without unnecessary words.

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?

Lists return fields since no output schema exists, providing necessary context. However, does not mention potential errors or whether additional fields might be present.

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% with basic descriptions for template_id and version_id. The description adds no extra guidance on how to obtain these IDs beyond what the schema provides.

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 verb 'retrieve', resource 'one dynamic template version', and lists included fields. Distinguishes from siblings like get_template and activate_template_version by specifying it's read-only and content-focused.

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?

Implies usage for when you need to view a specific version's content, but does not explicitly state when not to use it or mention alternatives among siblings like get_template.

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