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 discloses only that the key is discarded, but it does not explain what a valid Jira key shape is, what result is returned, or how invalid keys are handled.

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 two short sentences with no filler. The purpose is front-loaded, and 'Key discarded' adds a meaningful side-effect note without extra fluff.

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 tool with a large generic schema, no annotations, no output schema, and a critical missing key parameter, the description is far from complete. The agent cannot determine which parameter to use or what the tool returns, making the definition unusable in practice.

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 contains nine parameters but none of them is a Jira issue key or key-like input. The description refers to a 'key' that does not exist in the schema, and additionalProperties is false, so the agent cannot pass an undocumented key parameter. This is a critical mapping failure.

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 checks the shape of a Jira issue key, which is a specific verb and resource. It does not explicitly differentiate itself from sibling shape-checking tools, but the Jira qualifier makes the purpose distinct enough.

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?

There is no guidance about when to use this tool versus alternatives such as github-repo-shape or domain-shape. The description only states what the tool does, leaving the agent to infer usage context from the tool name.

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