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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does state that the key is discarded, which is useful privacy-relevant context, but it does not explain what the tool returns, whether it performs network access, or any other side effects. This is too sparse for a check-style 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 extremely concise: two short sentences with no filler. The primary purpose is front-loaded and the behavioral note follows immediately. It earns its place with minimal words.

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 a seven-property input schema, no annotations, and no output schema, this description is severely incomplete. It never explains which field contains the Jira key, what constitutes a valid shape, or what the result of the check will be, leaving the agent without enough context to call the 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?

The schema has high per-property description coverage, but the tool description does not map the 'Jira key' to any of the seven schema properties; none of them is labeled as a key. The description instead adds confusion by referring to a 'key' that does not exist in the input schema, so an agent cannot confidently determine which parameter to populate.

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 verb and resource: 'Check a Jira issue key shape.' This distinguishes it from sibling shape tools like domain-shape or github-repo-shape by naming the Jira key domain. However, the schema does not actually expose a 'key' property, which slightly undermines 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, nor does it mention exclusions or conditions. It implies use for validating Jira key shape, but that is left entirely to inference in a tool landscape with many similar shape-checking siblings.

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