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

With no annotations and a vague 'Key discarded' phrase, the description does not disclose return behavior, side effects, or what happens to the key. The tool's observable behavior is effectively opaque.

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 and front-loaded, but it is so under-specified that the second sentence, 'Key discarded,' adds confusion rather than clarity. Conciseness is achieved at the expense of meaningful content.

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 parameters, no output schema, and no annotations, this description is insufficient for an agent to call the tool correctly, interpret results, or understand the shape rules being checked.

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?

Although the schema has descriptions for 9 parameters, none of them corresponds to a Jira issue key, and most are unrelated boilerplate (e.g., city, feed, host). The description fails to map the stated purpose to any actual parameter.

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.' However, 'Key discarded' is ambiguous and the description does not identify which input parameter holds the key, leaving the exact purpose partially unclear.

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 provided on when to use this tool versus the many sibling shape-checking tools, nor any mention of appropriate contexts or alternatives.

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