update_listing_pricing

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

Annotations already convey that this is a mutating operation (readOnlyHint false) and idempotent (idempotentHint true). The description adds no behavioral context beyond that, such as whether unspecified fields are preserved, if this is a partial update, or any validation rules. It does not contradict the annotations.

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, front-loaded sentence beginning with the action and resource, followed by a short list of affected fields. No filler or redundant information, making it highly concise and well-structured.

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 pricing update with a fully self-documenting schema and no output schema, the description is adequate but incomplete in one key area: it does not explain partial-update behavior (e.g., whether omitted fields are left unchanged). Minor context about side effects would improve completeness.

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?

The input schema has 100% parameter description coverage, so the schema already documents each parameter. The description lists some fields (base price, cleaning fee, extra person fee, discounts) but adds no new meaning beyond grouping discounts; it does not compensate with extra context beyond the schema.

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 action ('Update pricing') and the resource ('for a listing'), naming specific price components (base price, cleaning fee, extra person fee, discounts). It is specific and unambiguous, though it does not explicitly differentiate from the sibling tool 'update_pricing'.

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 such as 'update_pricing' or 'update_listing'. The description only states what the tool does, leaving the choice of tool to the agent without explicit context or exclusions.

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