triage

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

Discloses key behaviors: it combines two operations, collects supporting issue numbers into cited_issue_numbers, and frames output as narration with caveats. No annotation exists, so this description carries the burden adequately.

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 concise and well-structured, with no redundant or irrelevant content.

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 what the tool does, how it behaves, and how the result should be presented. Minor gap: output structure is not described, but the narrative guidance compensates.

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 only parameter, text, is contextually described as 'new issue text' in the description, making its purpose clear even though the schema itself lacks a description.

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 the tool performs a full triage pass combining duplicate detection and component routing, which distinguishes it from sibling tools focused on individual subtasks.

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?

Explains that this is a single-call combination of find_duplicates and classify_component, implicitly indicating when to use it over the individual tools; also provides guidance on narrating caveats rather than presenting decisions as final.

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