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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false, so the safety profile is fully covered. The description adds the auth requirement (project API key), but that is largely restated by the projectApiKey schema field. No pagination behavior, default limit, result ordering, or truncation behavior is disclosed.

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?

Three short sentences, front-loaded with purpose and ending with auth. The filter enumeration is slightly redundant with the schema properties list, but as a scannable capability summary it earns its space.

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?

A 15-parameter read tool with 13% schema coverage and no output schema needs more than this. The description leaves the singular/plural filter duality unexplained, gives no default or maximum limit/offset behavior, and says nothing about result shape or ordering, which an agent must guess before invoking.

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 description coverage is only 13% across 15 parameters, so the description needs to carry the burden and it does not. It lists filter names (searchText, statuses, severities, assignee, assignees, labels, release, limit, offset, ordinalIds) without defining any of them, and never explains the critical singular-vs-plural pairs (status vs statuses, severity vs severities, assignee vs assignees) or what ordinalIds are. Listing names already visible in the schema adds little meaning beyond what the schema provides.

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?

"Search / filter TestChimp issues in the current project" gives a specific verb (search/filter) and resource (issues) plus project scoping. It also disambiguates from get-issue-details for single-issue retrieval. It stops just short of 5 because what a search returns (IDs? full records?) is never stated.

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 routes the agent to get-issue-details "for one issue by ordinal," which is a real alternative with a stated selection condition. No negative guidance is offered, e.g. when filters are unnecessary or whether calling with zero filters returns everything (required params = 0).

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