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

No annotations are provided, so the description carries the full behavioral burden. It only adds 'Key discarded,' which hints at non-retention, but it omits the return format, error behavior, validation rules, and whether the check is purely synchronous. This is minimal disclosure for a tool with no annotation support.

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 short and front-loaded, with the purpose in the first clause and the side-effect note in a compact second sentence. There is no filler, though the extreme terseness contributes to the lack of operational guidance.

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?

For a tool with no annotations, no output schema, and a mismatched parameter schema, this description is inadequate. It fails to identify the required input, the expected result, or how it differs from sibling validators, so an agent would be guessing at both invocation and interpretation.

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 schema lists nine optional parameters, but none is labeled as the Jira key, and the description does not map 'key' to any of them. An agent cannot determine which parameter to populate for the stated purpose. Schema coverage is high, but the schema appears disconnected from the tool's description.

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 names a concrete verb and resource: 'Check a Jira issue key shape.' This distinguishes it from sibling shape tools such as domain-shape or github-repo-shape. It is slightly weakened by not explaining what 'shape' means or what the tool returns, but the core purpose is identifiable.

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 about when to use this tool versus the many sibling shape-checking tools, nor any exclusions, prerequisites, or examples. An agent must infer usage entirely from the name and minimal description.

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