add_travel_item

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

Annotations supply openWorldHint=true and destructiveHint=false, so the description is not the sole carrier of the safety profile, but it adds nothing on top: no indication that this is a write that becomes visible on the public Travel page, no ordering/duplicate behavior, no validation rules, and no response description. For a creation tool with 19 fields this is a thin disclosure.

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?

A single front-loaded sentence with no filler. It is efficiently sized, though the brevity is partly the cause of the gaps elsewhere rather than a virtue earned by completeness.

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 19-parameter creation tool with no output schema and only partial annotation coverage, the description omits everything an agent needs beyond the bare action: required-vs-optional intent, which address fields matter for which type (a HOTEL vs a FLIGHT), whether the item is published publicly, and what happens on duplicates. It is not adequate for the tool's complexity.

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 53%, leaving roughly nine parameters (city, address1, address2, postal_code, display_order, email_address, contact_number, state_province, google_place_id) undocumented in both schema and description. The one thing the description does contribute – the list of item types – merely repeats the type enum already in the schema, so it adds no new meaning.

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 a specific verb (add) and resource (travel item) and enumerates the item categories, so an agent can tell it apart from list_travel_items, update_travel_item, and remove_travel_item by name alone. It stops short of explicitly naming those siblings or the parent resource (a wedding website's Travel page), which is the only thing keeping it from a 5.

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?

There is no when-to-use guidance, no mention of prerequisites, and no routing to the alternatives (update_travel_item for existing entries, add_poi for non-travel places). The agent must infer usage entirely from the verb.

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