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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description usefully clarifies that passing a null agent_bot_id performs a disconnect (an irreversible-looking action), but adds nothing about permissions, side effects on existing bot config, or error behavior.

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 front-loaded sentence with the primary action first and mode details in compact parentheticals. No filler or repetition of the title.

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 3-parameter mutation with no output schema, the description supplies the key invocation rule distinguishing connect/pause/disconnect. Missing only secondary context such as permission requirements and whether replacing an existing bot is destructive to prior configuration, which matters given destructiveHint=true.

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?

With 0% schema description coverage, the description must carry the load and largely does: it spells out the status enum (active|inactive) and, crucially, the combination rule that agent_bot_id null with no status means disconnect. Only inbox_id semantics and validity constraints on agent_bot_id are left unexplained.

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?

Specific verb+resource ('connect a bot to an inbox') that also enumerates the three operating modes it performs (connect, pause/resume, disconnect). An agent can distinguish this from read-oriented siblings like get_inbox_agent_bot or list_agent_bots without opening either schema.

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 each mode applies by tying status values and agent_bot_id null to connect/pause/disconnect, but it never names an alternative tool (e.g. get_inbox_agent_bot, update_agents_in_inbox) or states prerequisites. Usage is inferable but not explicitly guided.

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