collaboration_user_repo_invitation_decline

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

No annotations provided. The description notes it is a write operation requiring 'confirmed=true', but lacks details on side effects or outcomes. Some behavioral context is given.

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 front-loaded with the primary action, followed by the write operation requirement. No unnecessary words; efficient.

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?

Given the simple nature of the tool and clear sibling names, the description is complete. No output schema but return is likely straightforward.

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 coverage is 0%. The description mentions 'confirmed=true' but does not explain the 'invitationId' parameter. It adds some value but insufficient to fully compensate for missing schema descriptions.

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 a pending repository invitation') and specifies the agent identity ('on behalf of the current agent identity'). This distinguishes it from sibling tools like accept or list.

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 usage for rejecting a pending invitation but does not explicitly mention when not to use it or alternatives. However, sibling names provide context.

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