add_my_chat_participant

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

With no annotations, the description bears full burden. It states the action but does not disclose permissions, side effects, reversibility, or any behavioral traits beyond the parameter details.

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 docstring-style description is concise and well-structured, with each sentence adding value. No unnecessary words or repetition.

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 moderate complexity, the description covers basic purpose and parameters but omits preconditions, usage context, and output description. Since an output schema exists, the lack of return value information is acceptable, but 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 description adds meaning beyond the schema by enumerating role values ('owner', 'admin', 'member') and stating a default of 'member'. It clarifies chat_id as 'chat room ID' and participant_id as 'ID of user or agent', compensating for 0% 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 clearly states 'Add a participant to a chat room,' using a specific verb and resource. It distinguishes itself from removal tools but does not explicitly differentiate from sibling 'add_agent_chat_participant'.

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 lists required and optional parameters with defaults, providing usage guidance. However, it lacks context on when to use this tool versus alternatives (e.g., add_agent_chat_participant) and does not mention prerequisites or exclusions.

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