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

Annotations already indicate this is not read-only and not destructive. The description adds the constraint that the invitation must be pending and notes that the return value is a confirmation, which is useful but limited. It doesn't disclose side effects, permission requirements, or irreversibility, though the annotation set lowers the burden somewhat.

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?

The description is compact and well-organized, front-loading the action in the first sentence and then providing structured Args and Returns sections. Every line earns its place with no redundant or filler content.

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 one-parameter mutation tool with no output schema, the description covers the core action, the parameter, and the return type. It is sufficient for an agent to invoke the tool correctly, though adding a note about recipient versus sender roles would improve it further.

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?

The schema provides only an integer parameter name with no description, and schema description coverage is 0%. The description compensates by explicitly stating that invitation_id is 'ID of the invitation to decline,' giving the parameter clear semantic meaning beyond the raw schema.

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 clearly states the action ('Decline') and the resource ('a pending family invitation'), which is specific enough to understand the tool's core purpose. It doesn't explicitly differentiate from sibling tools like accept_family_invitation or revoke_family_invitation, but the verb itself makes the basic distinction obvious.

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?

No guidance is given about when to use this tool versus alternatives such as accept_family_invitation, send_family_invitation, or revoke_family_invitation. The description only restates the action without offering decision criteria or exclusions.

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