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

Beyond annotations (readOnlyHint, idempotentHint, etc.), the description adds meaningful behavioral context: it explains the tool returns notes, files, collaborators, and statistics, and instructs the agent to present only human-readable information (case number, subject, dates, notes). This discloses output characteristics and output filtering guidance, which is useful and not contradicted by 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 well-structured with headers and front-loaded key information, but it contains redundancy: the first paragraph is nearly identical to the 'When to use' section. It is still reasonably concise but not perfectly streamlined.

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 simple retrieval tool with one parameter and no output schema, the description is complete. It specifies what the tool returns (notes, files, collaborators, statistics), how to obtain the input (via fetch tools), and how to present the output. This gives the agent enough context to use the tool correctly without gaps.

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 includes a full description for the single parameter case_number with an example ('HYXTNJV'). The description duplicates this information without adding new semantics. Since schema coverage is 100%, the baseline is 3, and no extra value is provided by the 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?

The description clearly states the tool's function: 'Get full details of a support ticket by case number.' It distinguishes itself from sibling tools by explicitly directing users to fetch_open_tickets or fetch_closed_tickets first, clarifying that this tool is for retrieving complete details rather than listing tickets.

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 provides explicit when-to-use guidance: 'Use fetch_open_tickets or fetch_closed_tickets first to find tickets, then use this tool with the case number...' It also specifies what to do after retrieval ('Present only human-readable information'), giving clear context for use versus alternatives.

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