conversations_decline_shared_invite

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

With no annotations provided, the description carries the full burden. It only describes the basic action without disclosing side effects, permissions needed, or whether the action is reversible. For a safety-critical operation like declining an invitation, 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?

The description is a single sentence, making it concise. However, it sacrifices necessary detail; a slightly longer description with parameter context would be more helpful without being verbose.

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 tool's complexity (2 simple parameters) and presence of an output schema, the description should provide more context about expected behavior, such as what happens after declining (e.g., invitation removed) and how it differs from similar invite management tools. The current description falls short.

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% and the description does not mention any parameters. It fails to explain what 'invite_id' or 'target_team' represent, leaving the agent without crucial context for constructing valid arguments.

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 'Decline an invitation to a Slack Connect channel', providing a specific verb and resource. It implicitly distinguishes from accept/approve/deny siblings, though could be slightly more explicit about the target being a pending shared channel invitation.

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 vs alternatives like conversations_accept_shared_invite or conversations_request_shared_invite_deny. No conditions for use, prerequisites, or exclusions are mentioned.

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