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

No annotations are provided, so the description must carry behavioral transparency. It states the action ('attach') but does not disclose details such as idempotency, side effects, permission requirements, or error behavior. For a mutation tool, this is insufficient.

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, concise sentence that delivers the core message without unnecessary words. It is front-loaded and efficient, earning its place.

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 5 parameters (3 required) and no output schema, the description is too brief. It does not explain what 'attach' entails operationally, what constitutes a successful response, or how errors are handled. More context would be needed for safe and effective 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?

The input schema has 60% description coverage (3 of 5 parameters described). The description adds no parameter details beyond what the schema already provides, such as the meaning of 'capability_name' or the role of 'npub' and 'dpop_token'. This does not improve semantic clarity for the agent.

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 'Attach an issue to the capability it is about' uses a specific verb ('attach') and clearly identifies the resources ('issue' and 'capability'), making the tool's purpose unambiguous. It also distinguishes from sibling tools like cypher_link_capability_consumer and cypher_link_capability_to_patent, which link different entities.

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 description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusion criteria. Without context like 'use this when other linking tools are not appropriate', the agent lacks decision support for tool selection.

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