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

No annotations are provided, so the description carries full responsibility for disclosing behavior. The phrase 'Key discarded' suggests the input is not retained, but it does not clarify which key, nor does it explain the return value, side effects, or error handling. For a shape-checking tool with zero annotation support, this is a significant gap.

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 a single sentence, which is extremely short, but this is under-specification rather than conciseness. It omits essential information such as the target parameter and expected output format. A well-structured description would front-load the key parameter and behavior, which this does not.

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 the tool has 9 optional parameters and no output schema, the description should clarify what input to provide and what result to expect. It does neither. The presence of many sibling tools further increases the need for explicit guidance, which is entirely absent. The description is incomplete for any practical use.

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 each parameter has a basic description in the schema. However, the tool description adds no value beyond that and, critically, does not identify which parameter holds the Jira key. The schema entries like 'Git ref name' and 'City name' do not hint at a Jira key, so the agent cannot map the tool's purpose to any specific parameter. This undermines parameter semantics despite high schema coverage.

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 action ('Check a Jira issue key shape') and resource (Jira key), which clearly distinguishes the tool's purpose from siblings like domain-shape or github-repo-shape. However, it fails to identify which of the 9 input parameters contains the Jira key, leaving the agent uncertain about what to pass. This ambiguity lowers the clarity below what a specific verb+resource would normally earn.

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 alternatives like github-repo-shape or validate-json. There is no mention of prerequisites, contexts, or exclusions. The description is a single sentence with no usage context, so the agent must infer applicability from the name alone.

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