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

With no annotations, the description carries the full burden of behavior disclosure. It states the action (remove/cancel) but gives no details on reversibility, side effects, permissions, or how it differs from declining a received request. For a destructive mutation, 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?

One sentence, 12 words, front-loaded with the action verb and resource. No redundant information, perfectly sized.

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?

Simple tool with one parameter and no output schema. However, with no annotations and related sibling tools, the description could clarify the distinction between canceling an outgoing request and declining an incoming one (social_decline_connection). It leaves room for misinterpretation.

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 coverage is 100% with parameter description 'UUID of the connection to remove'. The tool description adds value by clarifying that connectionId can be either an existing connection or a pending request UUID, disambiguating the parameter beyond the schema's wording.

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 uses a specific verb 'Remove' and 'cancel' with resource 'existing connection' and 'pending request', clearly stating the tool's purpose. It distinguishes from siblings like social_accept_connection, social_decline_connection, and social_unfollow by covering both removal and cancellation.

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 explicit guidance on when to use this tool vs alternatives. The phrase 'cancel a pending request' implies outgoing requests, but it does not explicitly state that this is for requests the user initiated, nor does it contrast with social_decline_connection for incoming requests. Usage is implied rather than stated.

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