Decline Invitation

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

The annotations already declare readOnlyHint=false and destructiveHint=true, which the description aligns with ('decline' implies rejection/destruction). However, the description adds no extra behavioral context such as irreversibility, side effects, or authorization requirements beyond what annotations already provide.

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 a single concise sentence with no wasted words, and the core purpose is front-loaded. It lacks additional structure like examples or clarifications, but for its brevity it is 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?

For a tool with one parameter, no output schema, and simple semantics, the description is minimally adequate but incomplete. It does not explain what happens on success, how the token is used, or any caveats, relying heavily on the parameter name and annotations.

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 0% for the single 'token' parameter. The description does not explain what the token represents, how it should be obtained, or its role in declining the invitation, placing the full burden on the schema which provides only the name and type.

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 'Decline a workspace invitation' uses a specific verb (decline) and clear resource (workspace invitation). It implicitly distinguishes from sibling tools like acceptInvitation and getInvitation by the contrasting verb, making the purpose unambiguous.

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 provided on when to use this tool versus acceptInvitation or getInvitation. There is no mention of prerequisites, context, or exclusion criteria, leaving the agent to infer usage from the name alone.

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