List Defect Test Cases

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description's role is minimal. It confirms the read behavior and adds that only test cases currently linked are listed, but doesn't disclose details like pagination limits or rate handling.

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 a single, front-loaded sentence with no fluff. Every word earns its place, and it avoids unnecessary detail given the rich schema and annotations.

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?

Given the annotations (read-only, idempotent, non-destructive) and the presence of an output schema, the description is adequate. It could mention pagination or output format defaults, but the schema handles those. The description is sufficient for a simple read operation.

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?

All 4 parameters are fully described in the schema with defaults and ranges (100% coverage). The description adds no extra semantic context beyond what the schema provides, so it meets the baseline of 3.

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 'List test cases currently linked to a defect' uses a specific verb ('list') and resource ('test cases') with clear scope ('linked to a defect'), distinguishing it from siblings like 'list_test_cases' (lists all test cases) and 'link_defect_to_test_case' (creates a link).

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 does not explicitly guide when to use this tool versus alternatives. Usage is implied by the name and description, but no exclusions or context are provided, such as when to use 'list_test_cases' instead.

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