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

The phrase 'Key discarded' is a useful disclosure that the input is not retained, and 'check' implies a read-only validation. However, with no annotations and no output schema, it doesn't describe the return value, error behavior, or what happens when the shape is invalid.

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 sentences with no filler, but this is under-specification rather than effective conciseness. The description omits the operative parameter and expected result, making it too skeletal to support correct invocation.

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 large ambiguous parameter set, the description is incomplete. An agent cannot confidently determine which field to populate or 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?

Although schema description coverage is high, the description itself adds no parameter mapping. With many unrelated optional parameters, the agent cannot tell which one holds the Jira key; the schema's own descriptions are only partial clues.

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 concrete action and target: 'Check a Jira issue key shape.' The 'Jira' qualifier distinguishes it from sibling shape tools like domain-shape and github-repo-shape. It loses a point because no schema parameter is identified as the carrier of the Jira 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?

Provides no guidance on when to use this tool versus alternatives. It doesn't mention that the key should come from a Git ref or similar, and it gives no when-not-to-use or prerequisite context.

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