Get Issue Template

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

Annotations provide readOnlyHint=true, and the description adds valuable context about the output: 'The issue body lives in fieldTemplates.description; the template's own description describes the template itself and is usually empty.' This helps the agent interpret results correctly beyond a simple read-only assertion. No contradiction with annotations.

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?

Three sentences, each purposeful: first states the function, second gives a prerequisite action, third clarifies output structure. No redundancy, front-loaded with the core purpose.

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?

With a single parameter, read-only annotation, and an output schema present, the description provides sufficient operational detail. It explains how to obtain the ID, what the response includes, and a common caveat about the field names, making it complete for an agent.

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 covers template_id 100% with a description indicating it comes from issue_templates_get_all. The description adds only 'by its id,' which reinforces but doesn't meaningfully extend the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 description clearly states 'Get a single Yandex Tracker issue template by its id, including the field values it prefills,' which is a specific verb+resource+scope. It distinguishes itself from the sibling tool issue_templates_get_all by emphasizing 'single' and 'by its id.' The title is also expanded meaningfully.

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 explicitly instructs to 'Use issue_templates_get_all first to find the template id,' which is clear usage guidance and differentiates this tool from the listing tool. It also clarifies the semantics of `fieldTemplates.description` versus the template's own `description`, preventing misuse.

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