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

With no annotations present, the description carries the full burden and does meaningful work: it enumerates the returned fields and discloses the non-obvious behavioral trait that attachment/screenshot URLs are short-lived and signed. It stops short of stating permission requirements or not-found/error behavior, so it is strong but not exhaustive.

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 tight sentences: identity and key first, accepted input formats second, return contents third. No filler and nothing that restates the tool name.

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?

With no output schema and no annotations, the description compensates well by describing both the input formats and the return payload, including the short-lived signed URL caveat. Minor gaps remain around failure modes (invalid or nonexistent id) and the fact that this is a non-mutating read.

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 0% and the sole parameter has no description in the schema, yet the description fully compensates by spelling out five accepted issueId formats (#B-123, B-123, #B123, B123, plain 123) and clarifying that the id is an ordinal. This is exactly the compensating detail a low-coverage schema requires.

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?

States a specific verb ('Fetch') and resource ('TestChimp issue (bug)') with the keying mechanism ('ordinal id'), which cleanly separates it from siblings like create-issue, update-issue-status, and the various get-meeting-*/get-release-* tools. An agent can identify the target entity without opening the schema.

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?

Usage is implied by the fetch verb and the entity name, but there is no explicit when-to-use guidance, no mention of when the issue does not exist, and no note about interactions with the similarly-scoped create-issue / update-issue-status tools. Adequate but leaves routing to inference.

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