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

No annotations are provided, so the description must carry the behavioral disclosure burden. 'Key discarded' indicates the input is not retained, which is useful, but the description omits whether the tool is read-only, what it returns, how validity is signaled, and any error behavior. This is minimal disclosure for a check-like tool.

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: two sentences. It front-loads the core purpose and adds a minor behavioral note. It is arguably under-specified, but there is no wasted wording.

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 optional parameters, no annotations, no output schema, and a description that does not align with the schema, the tool is effectively unusable from the documentation. The description does not explain what 'shape' means, what a valid response looks like, which parameter to use, or how this relates to the listed inputs.

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, but the description introduces a 'key' concept that has no corresponding parameter in the schema. The listed parameters (url, path, zone, query, etc.) are unrelated to a Jira issue key, and the description does not map its primary concept to any schema field. This mismatch prevents an agent from knowing what to pass.

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-checking tools like github-repo-shape or domain-shape. However, the phrase 'Key discarded' is terse and the named resource is not reflected in any schema parameter, which slightly weakens clarity.

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?

The description gives no guidance on when to use this tool versus alternatives such as github-repo-shape or validate-json. It does not mention any conditions, exclusions, or alternatives. An agent must infer usage entirely from the name and schema.

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