Get Comment Templates

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

Annotations already mark readOnlyHint=true, and the description adds substantial behavior beyond that: 'Every page is retrieved by default; pass page to get a single page when the result does not fit the context window.' It also clarifies that queue filtering includes unbound templates usable everywhere. 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?

The description is front-loaded with the core purpose, then semantic context, usage timing, and parameter-specific guidance. Each sentence earns its place and the total length is appropriate for the tool's complexity.

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, paginated list endpoint with an output schema and fully documented parameters, the description covers the use case, queue scoping semantics, and context-window-aware pagination. It is sufficiently complete for an agent to select and invoke the tool correctly.

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 100%, so the baseline is 3. The description adds some contextual meaning for queue and page behavior, but it largely restates what the schema already describes (e.g., unbound templates returned with queue filtering, page used to limit results). It does not add new parameter-level detail.

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 the action and resource: 'Get the comment templates configured in Yandex Tracker.' It also explains what templates are and the intended use before adding a comment, which distinguishes this bulk-listing tool from the singular sibling comment_template_get.

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?

It explicitly says when to use the tool: 'Use this before adding a comment so it follows the team's current template instead of an invented one.' It also gives queue-filtering and pagination guidance, but it does not explicitly mention when not to use it or name an alternative like comment_template_get.

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