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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the mutation and irreversibility profile is covered structurally. The description's main addition - the shared_secret requirement per action - is essentially duplicated in the schema, and it adds nothing about error behavior or reversibility beyond the annotations.

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?

Two tight sentences, front-loaded with the source-of-truth list tool, then split cleanly by direction. Every clause earns its place with no redundancy or filler.

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 3-parameter mutation tool with a full schema and safety annotations, the description supplies the workflow context (list first, then act by direction) an agent needs. It omits success/failure semantics and reversibility, but those are largely implied by the destructiveHint annotation and no output schema is expected.

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 the schema already documents connection_request_id, action, and shared_secret, including the enum values and the shared_secret requirement per action. The description restates the same shared_secret/direction logic without adding syntax or format detail, so the baseline 3 applies.

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 gives a specific verb set (accept, decline, withdraw) against a specific resource (a LinkedIn connection request) and anchors the resource's origin to linkedin_list_connection_requests. An agent can distinguish this management tool from the sibling list tool and the send tool without opening any 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?

It clearly states where the input comes from (linkedin_list_connection_requests) and which action applies to each direction, effectively routing received vs sent cases. It stops short of naming an explicit alternative or exclusion (e.g. use linkedin_send_connection_request to create one), so it is strong context rather than full when/when-not guidance.

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