decline_chat_join_request

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

Annotations indicate the tool mutates state (readOnlyHint=false) but is idempotent (idempotentHint=true). The description adds no behavioral context beyond the literal action, such as effects on the user's request status or required permissions.

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, clear sentence with no fluff. It effectively states the tool's purpose without unnecessary words.

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 simple two-parameter tool with good annotations and schema coverage, the description is minimally adequate. However, it lacks context about when to use it (e.g., pending join requests) and what the consequences are, which 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 covers 100% of parameters with clear descriptions (chat_id and user_id). The description adds no additional parameter semantics, but the baseline of 3 is appropriate given high schema coverage.

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 chat join request' uses a specific verb ('decline') and a specific resource ('chat join request'). It clearly distinguishes from sibling tools like 'approve_chat_join_request'.

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 alternatives. It does not mention that it should be used for pending join requests, or that it requires admin privileges, or any exclusion criteria.

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