send_chat_action

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

No annotations are supplied, so the description carries the full burden. It does add genuine behavioral context by framing this as a status broadcast rather than a message, but it omits key traits: that the status is transient and auto-expires, that it does not appear in conversation history, and whether it needs to be refreshed or cleared.

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 short sentences with the core purpose front-loaded and useful inline examples. The bilingual duplication is redundant for a single-language consumer but is the only real padding.

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?

The tool is simple and an output schema exists, so return values need no explanation. However, for a no-annotation tool the definition still leaves the default chat targeting and the transient nature of the status unexplained, which an agent needs to invoke it sensibly.

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%, so the description needed to compensate and does not. It never mentions 'chat_id' at all, leaving the meaning of the nullable default (presumably the current chat) unexplained; the enum values for 'action' are self-descriptive, which is the only reason this isn't a 1.

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?

States a specific verb and resource: 'Broadcast ongoing bot status to the user,' with concrete examples (typing, uploading document, recording) drawn from the action enum. This is clearly distinguishable from siblings like send_text_message or send_local_document because it signals activity rather than content, though it never names those siblings explicitly.

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?

Usage is only implied: the phrase 'ongoing bot status' suggests calling it during a long-running operation, but there is no explicit when-to-use guidance, no note on how long the status persists, and no advice on pairing it with an actual send_* call. The agent must infer the workflow.

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