Enable Legacy Bot (B2B)

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

The description discloses a specific failure mode (422 BOT_NOT_INITIALIZED on clean apps), the precondition of a legacy bot, and a clear limitation. Annotations only say readOnlyHint=false and destructiveHint=false, so the description adds substantial behavioral context the annotations do not provide.

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 front-loaded with the core purpose and the critical 422 caveat, then follows with a 'Requires' section. It is somewhat long and repeats the alternatives to the Agents API in both the NOTE and the Requires section, which costs a small amount of conciseness.

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 tool with no output schema, the description tells an agent when the tool is valid, what precondition must be met, what error to expect otherwise, and exactly which sibling tools to use instead. This is complete enough to invoke the tool correctly in the B2B context.

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 input schema covers both parameters (appId and botTrigger) with descriptions at 100% coverage, so the structured data already carries the semantic load. The tool description does not add any parameter-level detail beyond what the schema provides, which matches the baseline for high schema coverage.

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 names a specific verb and resource: 'Enable the LEGACY per-app aiBot (B2B auth)'. It clearly distinguishes this tool from the v2/Agents family by emphasizing legacy-only scope and calling out the forward path via 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 description gives explicit when-to-use and when-not-to-use guidance: it works only for apps that already have a legacy dashboard-created aiBot, and API-created apps should use ethora-agents-create-v2 -> ethora-agent-invite-to-chat -> ethora-agents-activate-v2 instead. It also names ethora-b2b-app-bootstrap-ai as an alternative for the forward path.

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