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

Annotations already flag a non-readonly, open-world, non-idempotent write, and the description adds what those annotations cannot: two distinct returned links with different audiences, the organizer-email side effect, and the explicit 'does not hold or transfer money' boundary for chip_in. It does not cover quotas, editability, or what happens on repeat calls.

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?

Purpose and mechanics are front-loaded in sentence one, and the return-value statement closes the paragraph before any parameter detail. The occasion enumeration is long but it is the field the agent must fill, so it earns most of its length.

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 10-parameter nested write tool with an output schema, the description covers the flow, the money caveat, and the link semantics. Gaps are minor: it never says whether the card can be edited after creation or how the recipient receives the card if no organizer_email is supplied.

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 90%, so parameters are already well documented, including the chip_in sub-fields and currency defaults. The description adds only the high-level chip_in concept (pledge, pay organizer directly) and the audience distinction for the two links, so a baseline 3 is appropriate.

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 ('Creates an online group card ... for one person') and immediately explains the mechanics: one shared link, signers write messages, organizer delivers later by email/screen/print. The resource noun alone separates it from create_signup_sheet and create_date_poll, so an agent can route confidently.

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 long occasion list ('farewell, birthday, retirement...') plus the team/class/family framing gives concrete when-to-use context, and the chip_in sentence explains the money-collection variant. It stops short of naming alternatives or stating when to prefer create_signup_sheet instead, so it is clear but not exclusionary.

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