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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the safety profile is covered. The description adds little beyond the endpoint and inverse relation, such as side effects on message delivery or chat membership, but it does not contradict the annotations.

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?

A single sentence packs in the action, resource, endpoint, and inverse relationship with no wasted words. The most important information is front-loaded.

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?

For a simple destructive operation, the description is adequate, especially with annotations carrying the safety profile. But it leaves parameter semantics thin, gives no postcondition information, and relies on the reader to infer usage from the inverse relationship.

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 only 33%, and the description adds no meaning for `agentIdOrAddress` or `botInstanceId`. The endpoint template gives partial clues, but the description does not compensate for the two undocumented parameters, and `chatJid` was already explained in the schema.

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 states a specific verb and resource: 'Remove a BotInstance from a chat room,' and includes the exact endpoint. It also names `ethora-agent-invite-to-chat` as the inverse, making the tool's purpose immediately clear and distinguishable from related sibling tools.

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 inverse relationship with `ethora-agent-invite-to-chat` gives clear context for when this tool applies: it undoes an invitation. However, it does not explicitly state when not to use it or compare it to other bot-manipulation siblings such as bot-disable or instance-status.

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