manage_members

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

Discloses specific error code 9499 for ID mismatch, which is helpful. However, with no annotations, it fails to mention required permissions, reversibility, or other potential failure modes.

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?

Two sentences front-loaded with purpose, then a crucial usage hint. No wasted 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?

Sufficient for basic use but lacks output schema description, error handling details beyond one code, and permission requirements. Given tool simplicity and 100% schema coverage, it is adequate but not comprehensive.

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?

Adds valuable context beyond the schema by explaining the relationship between member_ids and member_id_type, including default behavior and error condition.

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 tool adds or removes members from a group chat, using specific verbs and resource. It implicitly distinguishes from sibling 'list_members' by being the mutation counterpart.

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?

Provides explicit advice on handling member_id_type mismatch and default behavior, but lacks direct comparison to alternative tools like 'list_members' or 'manage_task_members'.

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