get_issues_for_translation

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

Discloses automatic exclusion logic based on tags and bilingual structure, delimiter matching requirement, and default behaviors. No annotations exist, so description fully carries the burden.

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?

Well-structured with an Args section. Information is clearly presented; could be slightly more concise but effective.

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?

Complete for the tool's purpose. With an output schema present, the description adequately covers behavior and parameter semantics, linking to downstream usage.

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?

Despite 0% schema description coverage, the description explains all 6 parameters in detail, including defaults and purpose. Covers query, include_comments, max_results, exclude_translated, delimiter, and instance.

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 states 'Fetch issues with non-ASCII text for translation' with a specific verb and resource. It clearly distinguishes from siblings like get_issues by linking to translation workflow.

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 to call apply_translations with results. Provides context for when to use exclude_translated and delimiter. Does not explicitly state when not to use, but the purpose is clear.

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