Update Rappi address

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

The description adds the 'Requires explicit_user_intent' constraint, which is a behavioral requirement beyond what annotations already declare (destructiveHint=true). However, it does not elaborate on what the update entails, side effects, or any other behavioral traits, so the added transparency is minimal.

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 description is extremely brief (one sentence), but this brevity constitutes under-specification rather than effective conciseness. It omits essential usage and parameter information, making it a placeholder rather than a well-structured definition.

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?

For a tool with 12 parameters, a destructive action, and no output schema, the description is severely incomplete. An agent cannot infer what fields to populate, valid values, or the expected response. The only required field (address_id) is in the schema, but the rest is undocumented.

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 only 8% (only explicit_user_intent has a description), and the tool description provides no parameter-level detail for the 12 parameters. Fields like street, city, latitude, active, etc., remain entirely undocumented, so the description fails to compensate for the low 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?

The description states the action ('Update') and the resource ('a saved address') clearly. However, it does not differentiate this tool from siblings like rappi_create_address or rappi_set_active_address, so while the purpose is unambiguous, it lacks distinguishing context.

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?

No guidance is given on when to use this tool versus alternatives. The only directive, 'Requires explicit_user_intent,' is a prerequisite rather than a usage guideline, and no information about when not to use the tool or which sibling to prefer is provided.

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