create_address

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

With no annotations, the description fully discloses the polymorphic association, return behavior (re-fetched by id to avoid empty look), and uniqueness constraint with idempotent duplicate handling.

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?

Description is well-structured with clear paragraphs, each adding value. While slightly long, it front-loads the purpose and is efficient for the complexity involved.

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?

Completely covers the polymorphic behavior, duplicate handling, and return format. Given the complexity and the presence of an output schema, it provides all necessary context for correct invocation.

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 100% and provides good descriptions. The description adds context about the underlying polymorphic association but doesn't significantly augment parameter meanings beyond what the schema already offers.

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 'Create an address attached to a customer or supplier' and explains the polymorphic association, distinguishing it from update_address and delete_address.

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 explains the mechanism to identify the parent (addressable_type/addressable_id) and that exactly one of customer_id or supplier_id must be provided. Also covers duplicate handling, making idempotent behavior clear.

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