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

No annotations are present, so the description must carry the behavioral burden. It does disclose that the key is discarded, implying no persistence, and 'check' suggests non-mutating validation. However, it does not explain whether any network call is made, what the tool returns, or how errors surface, leaving a partial but incomplete picture.

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 terse and front-loaded: it states the purpose first, then adds a short retention note. Every sentence carries some information and there is no filler. It is concise, though the minimalism contributes to gaps in 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?

With no output schema and no annotations, the description needed to explain the return contract, the input-to-key mapping, and what 'shape' means. It does none of these. The seven heterogeneous parameters and the lack of a named Jira-key parameter leave the tool substantially under-specified.

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 has seven properties, each with its own description, so schema-level coverage is high. Yet none of the properties is labeled as the Jira key, and descriptions like 'Git ref name', 'HTTPS URL', and 'City name' do not map clearly to a Jira issue key. The description provides no guidance on which parameter to populate, undercutting the baseline score.

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 first sentence names a specific action and resource: 'Check a Jira issue key shape.' It is not a tautology and loosely distinguishes from sibling shape tools. However, 'shape' is undefined, and the second sentence 'Key discarded' is about data handling rather than purpose, adding a slight ambiguity.

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 about when to use this tool versus alternatives like github-repo-shape, domain-shape, or validate-json. There is no mention of context, exclusions, or conditions. 'Key discarded' hints at safe handling but not at usage selection.

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