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

With no annotations, the description carries the full burden. It discloses that the key is discarded (implying read-only), but does not state what the tool returns (e.g., boolean, status, or validation result) or any side effects. The behavior of 'check' is left ambiguous.

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 extremely short, two sentences, with no wasted words. It front-loads the core purpose. However, it is so brief that it sacrifices necessary detail, but that is captured under other dimensions.

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 9 parameters, no output schema, and no annotations, the description is grossly insufficient. It does not explain what constitutes a valid Jira key, what the tool returns, or how to use the parameters. An agent cannot reliably invoke this tool.

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?

Although the schema has 100% coverage with descriptions, the description itself adds no parameter semantics. The tool is about Jira keys, but the parameters (ref, url, city, feed, etc.) are unrelated, and the description does not indicate which parameter holds the Jira key or how they relate to the purpose. This is a critical gap for an agent.

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 states a specific verb ('Check') and a specific resource ('Jira issue key shape'), clearly distinguishing this from sibling shape-check tools like github-repo-shape or domain-shape. It also notes the key is discarded, which clarifies scope.

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 on when to use this tool versus alternatives. It does not mention that it is for validating Jira keys specifically, nor does it exclude other use cases. An agent must infer applicability 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.