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

Annotation Contradiction: annotations declare readOnlyHint=true, but the description describes a state-changing operation: 'Off detaches it from XMPP; on re-spawns the XMPP client live.' This directly conflicts with a read-only semantic. Because the description contradicts the annotation, the score is 1.

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, no filler, and the primary action is front-loaded. The effect of each status is immediately useful and compactly stated.

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 tool with an enum, the description is nearly complete: it names the resource, the parameter role, and the behavioral effect. The main gaps are the lack of explicit return-value expectations and the fact that the misleading readOnlyHint annotation undermines trust in the surrounding metadata, but the description itself gives enough to invoke the tool.

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 schema has 0% description coverage, so the description carries the semantic burden. It maps botInstanceId to the target BotInstance and status to 'on' or 'off,' while also explaining the runtime consequence of each status. It does not detail the ID format, but the enum and mapping are sufficient for correct invocation.

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: 'Turn a specific BotInstance on or off.' It clarifies the action beyond the title by explaining that 'off detaches it from XMPP; on re-spawns the XMPP client live,' which distinguishes this from generic status or list operations.

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 implies when to use the tool: whenever a specific BotInstance needs to be enabled or disabled at the XMPP level. However, it does not explicitly mention alternatives or conditions where another sibling tool like ethora-bot-enable-v2 or ethora-bot-instance-diag would be more appropriate.

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