Bot Instance Status

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

The annotations declare readOnlyHint=true, yet the description clearly describes a state-changing operation: 'Turn a specific BotInstance on or off' with detachment and re-spawning behavior. This is a direct contradiction, so the description provides misleading context about the tool's safety profile.

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, front-loaded with the main action and effect, followed by the necessary prerequisite. No filler or repeated schema information.

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 two-parameter toggle with an enum, the description provides the essential invocation context: what the action does and where to get the ID. However, the readOnlyHint annotation directly conflicts with the described behavior, and there is no output schema or mention of response/error behavior, leaving some ambiguity for an agent.

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 must compensate. It does: botInstanceId is tied to a specific source tool (`ethora-bot-instances-list`), and the status values 'on'/'off' are given behavioral meaning via detach and re-spawn. This adds real value beyond the raw 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 uses a specific verb and resource: 'Turn a specific BotInstance on or off.' It also explains the operational effect of each state ('Off detaches it from XMPP; on re-spawns the XMPP client live'), which clearly distinguishes this toggle tool from siblings like list, diag, or leave-chat.

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 gives clear context and a prerequisite: the bot instance id must come from `ethora-bot-instances-list`, and instances are created by `ethora-agent-invite-to-chat`. It does not explicitly state when not to use this tool or name alternatives, but the source-of-id guidance is practical and sufficient for a simple toggle.

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