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

The description conveys the state-changing nature ('decline/ignore'), and the annotations already supply destructive/idempotent hints. It adds scope (received vs sent) but no additional side-effect or safety details.

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?

Single clear sentence, no filler, front-loaded with the action and target.

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?

With complete schema coverage, idempotency and destructive annotations, and clear target scope ('pending received' vs sent), an agent has enough contextual clues to call it correctly, though it doesn't mention sibling alternatives.

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?

All three parameters are fully documented in the input schema (100% coverage), so the description adds no parameter-specific meaning, but no gap exists.

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?

States a specific verb and resource: decline/ignore a pending received connection request. The 'pending received' qualifier distinguishes it from sent-invitation tools, though it does not explicitly name sibling alternatives.

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?

Provides clear context ('pending received connection request') so an agent knows it applies to incoming, not sent, invitations. However, it gives no explicit 'when to use vs. not use' guidance or reference to alternatives like accept_invitation or withdraw_invitation.

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