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

With no annotations, the description carries the full burden of disclosure. It states 'Key discarded,' implying non-persistence, but does not describe the return value, error behavior, or any side effects. The parameter descriptions also mention discarding inputs, but the overall transparency is minimal.

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 brief (two sentences), but brevity without substance is under-specification. It does not front-load the essential information about which parameter to use or what the tool returns, so it fails to be efficiently informative.

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?

With 9 parameters, no output schema, no annotations, and a vague description, the tool is severely incomplete. An agent cannot determine which input to provide or what the tool will do with it, making correct invocation impossible without external knowledge.

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 those descriptions are inconsistent with the tool's stated purpose (e.g., 'City name for a public weather hint'). The tool description does not explain which parameter is the Jira key or how the parameters relate to the shape check, adding confusion rather than clarity.

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 verb ('Check') and a resource ('Jira issue key shape'), but it never specifies which of the 9 parameters carries the Jira key. The parameter list includes unrelated fields like city, feed, and json, so the tool's actual purpose is unclear. It also does not differentiate from sibling shape-checking tools like github-repo-shape.

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 any of the many sibling shape-check tools. There is no mention of conditions, alternatives, or exclusions, leaving an agent to guess which tool fits a given input.

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