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

The description discloses that the key is discarded after the check, which is a behavioral trait. However, with no annotations provided, the description carries the full burden. It does not mention whether the tool makes network calls, what happens with other parameters, or what the return value is. It is minimal.

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 concise, two sentences, and front-loads the purpose. Each sentence carries information. However, it is under-specified, which is not a conciseness issue but a completeness issue.

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 annotations, and no output schema, the description is severely incomplete. It does not explain the return value, the expected format of the key, or how the parameters relate to the check. An agent cannot confidently invoke this tool correctly.

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 baseline is 3. However, the description adds no information about the parameters, and the schema itself is confusing because none of the parameter names match 'key'. The description does not clarify which parameter should contain the Jira key, leaving the agent to guess. This reduces the score below baseline.

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 and resource: 'Check a Jira issue key shape.' This distinguishes it from sibling shape-checkers like domain-shape or github-repo-shape. However, the input schema includes many unrelated parameters, so the stated purpose is not clearly reflected in the schema, which could confuse an agent about what input to provide. So it is clear but not perfectly aligned.

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. The description does not mention any conditions, alternatives, or exclusions. The implied usage is when you need to validate a Jira issue key, but it is not stated explicitly.

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