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

Annotations are absent, so the description must disclose behavior. It mentions 'Key discarded,' implying the input is not retained, but it does not state whether the tool returns a boolean, performs network access, or has any side effects. The description leaves the agent unsure about output and operational characteristics.

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 very short and front-loaded with the purpose, which is good for conciseness. However, it omits critical information about which parameter to use and expected behavior, so it is under-specified rather than appropriately concise. It is not a tautology, but it does not earn a higher score because of the missing essential details.

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 9 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain which parameter is the Jira key, what shape is expected, what the return value is, or any side effects. An agent cannot correctly invoke this tool based on the description alone.

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 coverage is 100%, so the schema describes each parameter's type and meaning, but none relate to a Jira key. The description does not clarify which parameter is the key or how the Jira key shape is applied. Since the schema descriptions are for unrelated domains (e.g., city for weather, JSON for validation), the description fails to bridge the gap between the tool's purpose and its parameters.

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 and resource: 'Check a Jira issue key shape.' This distinguishes it from sibling shape-checkers like github-repo-shape. However, it does not indicate which of the 9 schema parameters holds the Jira key, and the schema lists unrelated fields (ref, url, city, etc.), creating ambiguity about how to invoke the tool. The purpose is clear in intent but not in practical usage.

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 is given on when to use this tool versus alternatives. It does not mention other shape-checking tools, nor does it describe the expected Jira key format or any prerequisites. An agent has no way to know whether this tool is appropriate for a given input or how it differs from sibling tools.

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