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

There are no annotations, so the description carries the burden. 'Key discarded' explicitly signals no persistence, which is useful, but the description does not disclose return behavior, error handling, or what 'shape' means. It offers only a minimal statelessness hint without enough operational detail.

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?

Two short sentences with no filler; the purpose is front-loaded. However, the extreme brevity borders on under-specification, so it is concise but not fully developed.

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 nine optional parameters, no output schema, and no annotations, this definition is not complete enough to invoke correctly. It never says which parameter should hold the Jira key or what the result looks like. The mismatch between the tool's stated purpose and its generic schema makes the description nearly unusable.

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?

Although schema coverage is 100%, the description does not connect the Jira key to any of the nine parameters. The schema descriptions (e.g., 'Git ref name', 'HTTPS URL to normalize or cite') are unrelated to Jira keys, so the description fails to add the needed mapping and leaves invocation ambiguous.

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?

States a specific verb and resource: 'Check a Jira issue key shape.' This is enough to distinguish it from sibling *-shape tools by resource, though it doesn't name alternatives or define the shape. The 'Key discarded' clause is confusing because no schema parameter is called '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?

No guidance on when to choose this tool over domain-shape, github-repo-shape, or validate-json. The description implies a validation use case but gives no context, preconditions, or exclusions. An agent has to infer usage from the tool name.

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