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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the core behavioral profile is covered. The description adds the constraint that the request must be 'pending' and 'received', but does not disclose additional behavioral details such as what happens if the invitation is already accepted or rate-limit implications.

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?

A single concise sentence that fully describes the tool's core purpose with no filler, front-loaded with the action on the resource.

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 simple accept-invitation tool, the description, combined with comprehensive schema documentation, an output schema, and annotations, gives an agent sufficient context to invoke the tool correctly. Minor gap: no explicit note about accepting only invitations in 'pending' status, which is implied but not stated as a precondition.

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% and all parameters are already well-documented in the schema. The tool description adds no parameter-level semantics, which is acceptable given the schema carries the full burden.

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 states a specific action ('Accept') on a specific resource ('pending received connection request'), and clearly differentiates from siblings like decline_invitation, list_received_invitations, and invitation_status. An agent can immediately understand what the tool does.

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 implies when to use the tool: when there is a pending received connection request to accept. It does not explicitly say when not to use it or name alternatives, but the context is clear enough given the sibling tool names.

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