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

The description goes well beyond the annotations by explaining exact side effects: existing users receive a copy of the Play, new users trigger an invite link, role restrictions exist ('Exec cannot mint a share'), and an approval workflow may gate first use. It also gives agent-facing guidance ('do not re-ask in chat'), which is valuable behavior context beyond the schema and annotations.

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 core behavior is front-loaded and the routing/approval sections are useful, but the description is dense with unexplained domain shorthand ('Operator door', 'the card is the yes') and could be structured more cleanly. Every section earns some place, but clarity suffers from jargon.

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 covers recipient behavior, role restrictions, and approval flow well. However, it doesn't specify what the tool returns for existing-user shares, doesn't clarify why playbook_id is optional in the schema, and leaves 'Operator door' unexplained, so an agent may still have gaps when deciding how to invoke it.

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 already has 100% description coverage for all parameters, so the baseline is 3. The description adds some conditional meaning for to_email (existing vs. new user), but this largely mirrors the schema's own description and adds little about companyId or playbook_id.

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 clearly identifies the action ('Send this Playbook') and specifies the recipient-dependent behavior (copy to existing user vs. returning an invite link for new users), which distinguishes it from generic send tools. However, it doesn't explicitly name alternative sibling tools, and it relies on domain jargon like 'Play' and 'Operator door' that may reduce immediate comprehension.

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 routing line 'Send a Playbook to a teammate or a new person → use this' gives explicit usage context, and the approval note explains how first-time authorization works. It doesn't explicitly name alternatives or state when not to use the tool, but the provided routing is sufficient for most selection scenarios.

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