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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Key discarded,' but does not state whether the operation is read-only, what happens on valid/invalid keys, what the return value is, or whether any network/disk access occurs. The schema hints at 'no disk access' for path, but the description omits this.

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 short, but the second sentence ('Key discarded.') is cryptic and does not earn its place because there is no corresponding key parameter. The brevity reflects under-specification rather than efficient conciseness.

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 9 optional parameters, no required parameters, no output schema, no annotations, and many sibling tools, a two-sentence description is drastically insufficient. It omits which parameter to pass, what 'shape' means, what output to expect, and how it differs from alternatives.

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 description coverage is 100%, so the baseline is 3, but the description fails to map its central concept ('Jira issue key') to any of the nine parameters. It adds no semantic value and actually confuses the parameter mapping, since no parameter is named 'key'.

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+resource ('Check a Jira issue key shape'), but the input schema contains nine generic fields (ref, url, city, feed, host, json, path, zone, query) with no 'key' parameter. This makes the actual input ambiguous and potentially misleading, since the agent cannot determine which field should receive the Jira issue key.

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?

There is no guidance on when to use this tool versus the many sibling shape/check tools (e.g., github-repo-shape, domain-shape, file-path-ok). No conditions, prerequisites, or alternatives are mentioned.

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