conversations_request_shared_invite_deny

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

No annotations are provided, so the description carries full burden. It only says 'deny', implying a mutation, but doesn't disclose auth requirements, side effects (e.g., whether it removes the user), or if the optional 'message' parameter affects behavior. The lack of transparency hinders safe usage.

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, which is concise. However, it could include additional critical details without becoming verbose. It achieves basic conciseness but lacks depth.

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 involvement in invite management and the existence of numerous sibling tools (e.g., approve, decline, list), the description is too sparse to fully contextualize its role. The output schema exists but isn't referenced, and parameter semantics are missing. An agent could easily misuse this tool without additional context.

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%, meaning the description adds no information about the two parameters. 'invite_id' is required but not explained, and the 'message' parameter's purpose is unclear. The agent must rely solely on the schema names, which are insufficient.

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: 'Deny a shared channel invite request.' It uses a specific verb ('deny') and resource ('invite request'), making the purpose clear. However, there is a sibling tool 'conversations_decline_shared_invite' that might overlap in meaning, and the description does not differentiate between them, so it's not a 5.

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 provides no guidance on when to use this tool versus similar tools like 'conversations_accept_shared_invite' or 'conversations_decline_shared_invite'. There is no mention of prerequisites, such as needing the invite ID, or consequences like irrevocability.

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