Update listing

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

Annotations indicate a write operation and openWorldHint, but the description does not elaborate on potential side effects. It clarifies the PUT method and partial update behavior, which is adequate but not thorough.

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?

Two sentences, no fluff, front-loads the purpose and usage pattern. Every word is useful.

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 the high parameter count (15) and no output schema, the description is too minimal. It lacks information about response, validation rules, or handling of nested structures like attributes. Comparable tools likely need more guidance.

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?

With only 7% schema description coverage, the description adds almost no parameter-level detail. It does not explain the meaning of any field beyond the schema's sparse descriptions, failing 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 explicitly states the verb 'Update' and the resource 'existing listing', and includes the HTTP endpoint. It clearly distinguishes from sibling tools like create_listing or delete_listing.

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 specifies partial update semantics ('Provide only the fields you want to change'), guiding the agent on how to construct the request. No explicit when-not-to-use or alternatives, but the context is clear.

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