add_address

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

With no annotations, the description carries the full behavioral burden. It discloses the auth requirement, which is useful, but says nothing about side effects, whether the new address becomes a default, duplicate handling, or validation behavior for a mutation operation.

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 purpose sentence is front-loaded and the argument list is structured and scannable. Nothing is redundant, though the bare 'Args:' block is functional rather than polished.

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?

An output schema exists, so return values need not be explained, and all parameters plus the auth requirement are covered. However, for a mutation tool with no annotations, the description leaves behavioral gaps (side effects, default-address semantics) that would matter to an agent.

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 0%, so the description must compensate, and it largely does: it documents all 7 parameters with clarifications like 'State abbreviation (e.g. NY, CA)' and 'Label for the address (e.g. Home, Work)'. It does not mark which of the fields are optional, but the per-field guidance is solid.

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 ('Add a new delivery address'), making the operation immediately clear. It does not explicitly differentiate itself from the read-side sibling get_addresses, but the write intent is unambiguous.

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 a prerequisite ('Requires authentication') and the usage is implied by the name, but it never states when to use this versus alternatives like get_addresses, nor any conditions under which adding should not be done.

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