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

There are no annotations, so the description must carry the full behavioral burden. 'Key discarded' hints that the tool is non-persistent and probably side-effect-free, but it does not disclose what the tool returns (e.g., a boolean, normalized key, error message) or any consistency guarantees. The behavioral detail is extremely thin.

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 only two sentences and is very brief, which is good for conciseness. However, the brevity comes at the cost of clarity, and the second sentence 'Key discarded' adds little actionable information. The structure is acceptable but the content is too sparse to be genuinely helpful.

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 no annotations, no output schema, and a parameter schema that is clearly misaligned with the tool purpose, the description is far from complete. An agent lacks even the most basic information needed to call the tool: which parameter carries the Jira key, what the response looks like, and what 'shape check' actually entails. The sibling list reinforces the shape-checking category but does not compensate for these missing details.

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 seven parameters, none of which is named 'key' or explicitly described as a Jira issue key. The description says 'Key discarded,' but the agent cannot determine which schema field to populate. The schema property descriptions are about unrelated concepts like Git refs, URLs, city names, and JSON text, so they do not help map the intended input. This is a serious gap that makes correct invocation nearly impossible for an agent.

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 ('Check') and resource ('a Jira issue key shape'), making the tool's core purpose immediately clear. It is distinct from the sibling shape-checking tools because it explicitly names Jira. However, it does not explicitly differentiate itself from closely related tools like github-repo-shape or domain-shape, so it stops short of a 5.

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 provides no guidance on when to use this tool versus alternatives. With a sibling list full of similar shape-checking utilities, an agent is left to infer from the tool name that this is the Jira-specific shape checker. No exclusions, prerequisites, or alternative routing are mentioned.

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