add_party_address

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

Annotations indicate a non-read, non-destructive write. Description adds behavioral context: atomic PUT operation and detailed validation behavior for the country parameter (rejection on invalid entries, normalization). However, no mention of side effects on existing data.

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 concise sentences: first states purpose, second gives usage guidance. No extraneous information, front-loaded and 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?

Covers primary purpose, usage alternative, atomicity, and country validation. Missing details on optionality of parameters (though schema shows none required), return value, and error cases beyond country.

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 coverage is low (29%). The country parameter description is exceptionally detailed, adding validation rules and examples. Other parameters like street, city, state, zip lack any description in the schema or tool description, leaving gaps.

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 states it appends a single postal address to a party, distinguishing itself from update_party.addresses by explicitly recommending its use for single-entry adds.

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?

Provides when-to-use guidance (single-entry adds instead of update_party.addresses) and mentions atomicity, but does not explicitly exclude scenarios like adding multiple addresses or state prerequisites such as party existence.

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