list-defects

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

No annotations are provided, so the description carries the full burden. It does not disclose any behavioral traits such as pagination, result limits, default sorting, or return format. The parameters page and size hint at pagination, but the description does not confirm or explain. This is a critical gap.

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 very short (one sentence), which is concise. However, it omits essential information, making it under-specified rather than efficiently informative. Appropriate sizing would require more detail to be useful.

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 three parameters, no output schema, and no annotations, the description is highly incomplete. It fails to explain pagination, return type, required permissions, or how to handle errors. The sibling tools are numerous, and this description does not help the agent select 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 coverage is 33% (only projectId described). The description adds no meaning to page or size parameters (e.g., pagination, defaults). It repeats 'project' context but does not compensate for the missing parameter descriptions. The description adds minimal value beyond the schema.

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 defects in a project' clearly states the verb and resource. The name 'list-defects' distinguishes it from sibling tools like get-defect (single) and create-defect. However, it does not explicitly differentiate from other list tools but achieves clarity through the resource name.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., get-defect, search-test-cases). There is no mention of prerequisites, filters, or when not to use it. The agent is left to infer usage from the name alone.

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