Send Typing Indicator

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states what the tool does. It does not mention side effects, whether the indicator is ephemeral, or any interaction with the other participant. This is minimal and lacks transparency beyond the basic action.

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, well-formed sentence with no redundant phrases. It front-loads the action and specifies the target, and the parenthetical adds essential clarification without 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?

Given the tool's simplicity and full schema coverage, the description provides the core function, but it lacks usage context and behavioral details that would make it complete. The output schema exists, so return values are covered, but the missing guidelines and transparency make it minimally sufficient rather than fully complete.

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 100% for both parameters (thread_id and typing). The description's parenthetical 'typing_on / typing_off' restates the schema's boolean description but adds no new semantic detail. Therefore, the baseline score of 3 applies.

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 sends a typing indicator to a conversation, with the parenthetical 'typing_on / typing_off' clarifying the two possible states. This uses a specific verb and resource, distinguishing it from sibling tools like send_message or mark_conversation_seen.

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, nor does it mention any prerequisites or context (e.g., 'send before composing a message'). The sibling context exists but the description itself offers no explicit usage instructions.

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