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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does reveal that the key is discarded, but it does not mention side effects, network access, return behavior, or error handling. The schema descriptions also repeat discarding details but add little else.

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 only two sentences and wastes no words; purpose and discard behavior are front-loaded. While it is under-specified overall, as a structural matter it is concise and readable.

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 annotations, no output schema, and no link between the stated purpose and the actual parameters, the description is far too sparse for an agent to confidently select and invoke the tool. The mismatched seven-field schema makes this especially incomplete.

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 input schema exposes seven optional string properties with generic descriptions, and the tool description never identifies which property is supposed to carry the Jira key. An agent cannot determine whether to pass ref, url, path, or another field. The schema's descriptive coverage does not help because none of the fields are described as Jira-key inputs.

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 gives a specific verb and resource: it checks the shape of a Jira issue key, which distinguishes it from sibling shape tools like github-repo-shape or domain-shape. However, the term 'key' is never connected to any input property, leaving a high-level but incomplete purpose.

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 phrasing implies the tool should be used when validating a Jira key shape is needed, but it provides no explicit context about when not to use it or which sibling shape tool to prefer. There are no stated alternatives or exclusions.

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