xtalk_presence

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

No annotations provided, so description bears full weight. It reveals the deadlock detector dependency and auto-recovery impact, which is good. However, it does not explain behavior for optional parameters (room, target_msg_id) or error conditions.

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, no fluff. First sentence states purpose, second gives usage guidance and warning. Every part earns its place.

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?

Covers core purpose and usage of the required parameter, but omits explanations for two optional parameters. Given the tool's simplicity and no output schema, the description is partially complete but has a notable gap.

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%, yet description only explains the mode parameter's enum values. The 'room' and 'target_msg_id' parameters remain undocumented, leaving agent to guess their purpose. This is a significant gap.

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 'Set your presence mode manually,' specifying the verb (Set) and resource (presence mode). It also lists specific modes and their intended use, distinguishing from sibling tools like xtalk_listen or xtalk_wait which are different operations.

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?

Explicitly describes when to use each mode ('Use `listening` before entering Monitor listen loops...') and warns about consequences ('mis-declaring it will break auto-recovery'). Provides clear context for deciding when to invoke this tool.

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