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

Beyond the annotations, the description discloses important side effects: accepting creates a public asynchronous room, the recipient speaks first, there is a 10-message intro limit, per-turn and overall time windows, and no charge. It does not detail what happens on decline or cancel, but the main behavioral profile is clearly conveyed.

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 tight and front-loaded: the primary action is stated first, followed by the most important acceptance conditions and constraints. Every sentence adds operational value, from room creation eligibility to message and time limits to the no-charge note.

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 mutation tool with no output schema, the description covers the essential behavioral outcomes and constraints needed to invoke it correctly. It could clarify what happens when conditions are not met or describe return values, but the core acceptance, decline, and cancel semantics are sufficiently complete for a low-complexity enum action.

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%, but the description compensates by explaining the decision semantics: accept, decline, and cancel, plus the conditions and consequences of acceptance. It also clarifies that cancellation applies to invitations the user sent, adding meaning beyond the bare enum 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 uses a specific verb and resource: 'Accept or decline a received invitation, or cancel one you sent.' This clearly identifies the tool's operation and distinguishes it from sibling tools like speedbot_invite, speedbot_offer_intro, and speedbot_respond_intro, which handle different invitation or intro actions.

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 for when the tool applies: handling received invitations via accept/decline and sent invitations via cancel. It also states the eligibility and busy conditions under which acceptance creates a room, but it does not explicitly name alternative sibling tools or exclusion cases.

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