send_typing

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

Without annotations, the description only mentions displaying typing status for a few seconds. It does not disclose that the 'action' parameter can indicate other statuses (e.g., recording audio) or that 'cancel' stops the indicator. No information about side effects or cancellation behavior.

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 short and front-loaded, but it is a single sentence that could be broken into structured elements for clarity. It is concise but lacks parameter explanations.

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 has three parameters and an output schema, the description is incomplete. It does not cover the 'action' parameter's rich enum or the return value, leaving the agent missing critical usage details.

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 context for the 'seconds' parameter (duration) but fails to explain the 'chat' and 'action' parameters, despite 0% schema coverage. The 'action' enum with many options is completely ignored in the description.

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 displays a 'typing' status in a chat for a duration, and the name 'send_typing' reinforces this. It distinguishes from sibling tools like 'send_message' which actually sends messages, not just indicators.

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?

No guidance on when to use this tool versus alternatives (e.g., using 'send_message' directly). The description implies usage for showing typing activity but lacks explicit context or exclusions.

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