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

The description states 'Key discarded,' which implies the input is not stored, but this is minimal and ambiguous since it doesn't identify which key. There is no mention of side effects, network access, or return value. With no annotations, the description carries the full burden of disclosure and fails to provide sufficient behavioral context.

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 concise (two short sentences), which is good, but it is under-specified. It lacks essential structure such as a mapping of the key parameter or an example of the expected key shape. Conciseness is achieved at the expense of necessary detail, so a mid-range score is appropriate.

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 nine optional parameters and no output schema or annotations, this description is severely incomplete. It doesn't explain which parameter is the key, the expected format (e.g., 'PROJ-123'), the return type, or any behavioral details. The agent has no way to correctly invoke this tool based on the description.

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 coverage is 100%, so each parameter has a description, but the tool description does not clarify which parameter is the Jira key. The agent cannot map the purpose to a specific parameter, and the description adds no value beyond the schema. The baseline of 3 for high coverage is lowered because the description creates ambiguity about parameter usage.

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'), which distinguishes it from sibling shape-checkers like domain-shape or github-repo-shape. However, it does not specify which of the nine input parameters holds the Jira key, so the agent cannot determine how to supply the key. This vagueness reduces 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?

No guidance is provided on when to use this tool versus alternatives such as domain-shape or github-repo-shape. There is no mention of prerequisites, selection criteria, or scenarios where this tool is preferred. The description leaves the agent to infer usage, which is inadequate.

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