add_party_email_address

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

No annotations provided. Description mentions atomicity and one PUT, but does not disclose side effects (e.g., duplicate handling), required permissions, or error states. With zero annotations, more behavioral detail is needed.

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 sentences with no superfluous words. First sentence states action and atomicity; second provides usage advice. Highly efficient.

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?

No output schema and no annotations, but tool is simple (append one email). Description is adequate for distinguishing from siblings and basic usage, but lacks completeness on error handling or response. Minimum viable for this complexity.

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 33% (only 'type' has a description). Description does not explain 'partyId' or 'address' beyond tool purpose. The regex and format on 'address' are self-documenting, but the description adds minimal value. Fails to compensate for low schema coverage.

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?

Clearly states the verb 'Append' and resource 'single email address to a party'. Distinguishes from sibling update_party.emailAddresses by specifying that it is used when adding exactly one entry, and contrasts with the bulk array behavior.

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?

Explicitly states when to use this tool instead of update_party.emailAddresses (when adding exactly one, because bulk is append-only). Does not mention exclusions or alternatives besides update_party, but provides clear context for decision.

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