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

Annotations already flag destructive=true and idempotent=false, so the description's value is in the specifics it adds: conversations are closed, upcoming hosted and attended mocks are cancelled, and other participants are notified. That is exactly the kind of consequence detail an agent needs before calling a destructive tool. It stops short of 5 because it doesn't say whether the cancelled interviews can be recovered or rebooked, only that the handle survives a rejoin.

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 tight sentences: the action first, then the consequences, then the rejoin caveat. Every clause carries information an agent would otherwise have to guess at; nothing is repeated from the title or annotations.

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 zero-parameter, destructive tool with no output schema, the description covers action, side effects, third-party notification, and re-entry behavior, which is nearly everything needed to call it safely. Minor gaps remain around recoverability of the cancelled mock interviews and any confirmation or membership preconditions.

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 tool takes no parameters, so there is nothing for the description to disambiguate. It correctly avoids inventing parameter semantics and instead spends its words on effects, which is the right allocation for a zero-arg tool.

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?

States a specific verb and resource ('Leave the interview buddy network') and immediately enumerates the scope of what leaving entails: closing buddy conversations and cancelling upcoming mock interviews hosted or attended. This clearly separates it from sibling tools like buddy_join, buddy_status, or buddy_mock_cancel without needing the 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 gives clear context for when this is the right action and hints at the inverse path with 'Rejoining later restores the same handle,' effectively pointing to buddy_join. It does not explicitly state exclusions or prerequisites (e.g., whether an active membership is required), so it stops short of full when/when-not guidance.

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