conversations_decline_shared_invite

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

No annotations are provided, so the description carries the full burden. It only states the basic action ('Decline an invitation') without disclosing behavioral traits like permission requirements, side effects (e.g., invitation becomes invalid), or whether it can be undone. For a mutation tool, this is insufficient.

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?

A single, short sentence with no wasted words. It is very concise, but the extreme brevity sacrifices completeness for conciseness. Still, it front-loads the purpose clearly.

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 action and presence of an output schema, the description is minimally adequate. However, it lacks context about the Slack Connect invitation flow, prerequisites (e.g., must be the invitee), or error conditions. For a tool with many sibling operations, more context would improve completeness.

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 input schema already describes both parameters with 100% coverage. The description adds no additional context about how parameters relate to the action (e.g., how to obtain invite_id). Baseline 3 is appropriate since schema covers meaning, but no extra value from description.

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 an invitation') and the resource ('Slack Connect channel'). The verb-resource pair is specific and directly matches the tool name, distinguishing it from siblings like accept or approve.

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 on when to use this tool versus alternatives such as conversations_accept_shared_invite or conversations_approve_shared_invite. The description does not mention prerequisites or context for using decline over other operations.

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