alonomic_add_saved_address

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

No annotations provided. The description indicates a POST mapping and 'Save a new pickup address,' implying creation. It does not disclose error conditions, idempotency, side effects, or permissions beyond the absence of the enable_ordering gate.

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 stated first, then endpoint, then parameter list. The Persian sentence is redundant for English agents but does not harm clarity. The parameter list is well-organized but slightly long. Overall 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?

Given 10 parameters, 0% schema coverage, no annotations, and an output schema (context indicates it exists), the description adequately covers the tool's function and parameter semantics. It does not explain output, but output schema presumably handles that. No major gaps.

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 0%, so the description carries full burden. It lists all 10 parameters with brief but helpful explanations (e.g., lat: 'Latitude (-90..90)' adds constraint, address: 'Free-text street address'). While not exhaustive, it adds meaningful context beyond the schema's names and types.

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 'Save a new pickup address,' specifies the endpoint, and distinguishes this address-book operation from delivery tools. It explicitly mentions it is not gated by enable_ordering, separating it from other tools.

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 description states when to use (address book, not delivery) and explicitly says 'NOT gated by enable_ordering,' giving context on prerequisites. However, it does not explicitly compare to sibling tools like alonomic_delete_saved_address or alonomic_get_saved_addresses, nor provide when-not-to-use scenarios.

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