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

No annotations are provided, so the description carries the full burden. The only behavioral disclosure is 'Key discarded,' which hints at non-persistence. It does not explain what 'shape' means, whether validation is syntactic or semantic, what the return value is, or any side effects. This is severely lacking for a tool with zero annotation coverage.

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 at two sentences, but it is under-specified rather than efficiently concise. It omits essential information such as valid key formats, which parameter to use, and the result format. Conciseness without substance earns a low score.

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 the tool has 9 parameters, no output schema, and no annotations, the description is wholly inadequate. It does not connect the schema parameters to the Jira key check, does not specify expected input/output behavior, and leaves the agent guessing. This is a major gap for a tool of this complexity.

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 description coverage is 100%, so the baseline is 3. The description adds no parameter-specific information beyond what the schema already provides, and it does not clarify which of the 9 parameters is the Jira key. The phrase 'Key discarded' applies to many parameters but does not help map them to the tool's purpose.

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 clear purpose: 'Check a Jira issue key shape.' This is a specific verb and resource, and the name reinforces it. However, it does not differentiate from sibling shape-checking tools like domain-shape or github-repo-shape, and it leaves unclear which parameter represents the Jira key.

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 on when to use this tool versus alternatives. The description does not mention any conditions, exclusions, or sibling tools. Given many similar shape-checking siblings exist, an agent has no basis to choose this one.

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