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

The description discloses atomicity ('Decisions and grants change atomically') and idempotency ('A repeated matching response returns the recorded decision and current permission without changing a later grant or revocation'), which go beyond the annotation readOnlyHint=false. This adds valuable behavioral context for the agent.

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 two sentences and packs the essential information without excessive detail. It is well-structured and front-loads the core action.

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 covers the core behavior and important edge cases (idempotency). However, it does not specify prerequisites like the request being pending or behavior for invalid IDs. Given the output schema exists and annotations are minimal, it is reasonably complete but has some gaps.

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 description does not explain the parameters beyond the general action. It does not explicitly state that 'allowed' is a boolean meaning true=allow and false=deny, nor that 'request_id' is the ID of the pending request. With schema coverage at 0%, the description should compensate, but it does not.

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 clearly states the tool's function: it allows or denies a pending connection request, and explains the consequences (granting or revoking permission). This distinguishes it from sibling tools like request_connection (creating a request) and allow_sender (which may be a different mechanism).

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 does not explicitly state when to use this tool versus alternatives. It implies the context (recipient responding to a pending request) but does not mention when to use it instead of other tools like allow_sender or list_connection_requests. No exclusions are given.

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