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

Annotations already declare destructiveHint=true and readOnlyHint=false, covering the mutation nature. The description adds the constraint that the request must be pending and directed at the calling user, and specifies the exact source for the ID, giving operational context beyond the safety hints.

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 sentences with no filler: the first states the purpose, the second tells how to obtain the parameter. Purpose is front-loaded and every word earns its place.

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?

This is a simple one-parameter tool with an output schema present. The description covers the operation, the origin of the required ID, and implicitly its scope (pending, calling user). Nothing essential for correct invocation is missing.

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 the parameter description already includes the 'NOT the other user's id' clarification and the list-source guidance. The tool description's mention of friendId from play_list_pending_friends is redundant with the schema, so it adds minimal new meaning beyond what the schema provides.

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 verb ('Decline') and resource ('pending friend request') scoped to the calling user, and the qualifier 'pending' plus the source list clearly differentiates it from accept, cancel, and remove siblings. An agent knows exactly what this tool does and how it differs from peers.

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 explicitly instructs to pass friendId from play_list_pending_friends, and the schema description reinforces that play_list_pending_friends is for accept/decline while play_list_my_friends is for remove, effectively routing the agent to the correct list and tool for this operation.

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