update_pricing

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

Annotations indicate the tool is idempotent and non-destructive, and the description does not contradict these. The description adds behavioral context by highlighting two update modes (specific dates vs. default base price), but it does not disclose edge cases such as parameter precedence or what happens if conflicting parameters are provided.

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 a single sentence that directly states the tool's purpose. It is concise, free of fluff, and efficient in conveying the key information.

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 straightforward write operation with no output schema, the description covers the core behavior. However, it lacks information on parameter interaction (e.g., what if both basePrice and price are supplied), and does not clarify how it differs from the similar sibling 'update_listing_pricing'. This leaves some gaps for 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?

Since all parameters have descriptions in the schema (100% coverage), the baseline is 3. The description adds conceptual grouping by distinguishing date-specific pricing (price, dateFrom, dateTo) from default basePrice, but it does not add significant detail beyond what the schema already provides.

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 the tool's function: updating the base price for a listing, either for specific dates or the default base price. It names the resource and scope, but does not distinguish itself from the sibling tool 'update_listing_pricing', which may overlap in functionality.

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 provided on when to use this tool versus alternatives like 'update_listing_pricing'. The description implies usage by stating what it does, but there is no explicit context, exclusions, or comparison to sibling tools.

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