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

No annotations are provided, so the description carries the full burden and does: it warns that LinkedIn blocks re-inviting the same person for up to three weeks, that the action cannot be undone, that it is limited per day, and that it handles one person at a time. These are exactly the side effects and rate constraints an agent needs before committing.

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?

Front-loaded with the action and its precondition, then alternatives, then warnings. It runs a bit long and the trailing responses block mostly restates boilerplate, but nearly every sentence carries usable guidance.

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?

For a one-parameter mutation tool with no annotations and no output schema, the description covers trigger, exclusion, prerequisite lookup, confirmation requirement, irreversible side effect, and rate/quota limits. An agent has everything needed to call it safely and correctly.

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 0% and the schema only declares a bare string, so the description has to compensate — and it does by identifying the value as a draft_ handle sourced from list_sent_connection_requests. It doesn't describe the handle's format beyond the draft_ prefix, but the provenance guidance is the operationally important part.

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?

Names a specific verb (withdraw) and resource (connection request) and scopes it to requests already sent and still pending. It explicitly contrasts with cancel_scheduled, which handles queued requests, so the agent can discriminate it from siblings without opening the schema.

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?

Gives an explicit trigger condition (user asks to withdraw / retract / take back / unsend), an explicit exclusion (use cancel_scheduled for queued requests), and prerequisites (look up via list_sent_connection_requests, confirm the person with the user). Nothing is left to inference.

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