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

With no annotations, the description carries the behavioral disclosure burden. It states that the key is discarded, which implies a non-retaining validation operation. It does not mention the return value, failure behavior, network usage, or whether any other side effects exist.

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 short sentences with no filler, and the main purpose is front-loaded. The second sentence is terse and a little cryptic, but still earns its place by adding a privacy/behavioral signal.

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?

The description is too thin for reliable invocation: there is no output schema, no expected Jira key pattern, no mapping to the seven schema parameters, and no usage context. An agent would have to guess which parameter contains the key and what the tool returns.

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 has seven string parameters, none named 'key', and none clearly maps to a Jira issue key. The description uses the word 'Key' but fails to link it to any schema property, so an agent cannot confidently choose which field to populate.

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 names a specific verb and resource: 'Check a Jira issue key shape.' The tool name reinforces this. However, it does not define what makes a valid Jira key shape or which input parameter carries the 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?

The domain is clear from 'Jira issue key', so an agent can infer it is the Jira-specific sibling of tools like github-repo-shape or domain-shape. There is no explicit statement of alternatives or when not to use it, but the resource name gives enough context for basic selection.

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