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

Annotations already declare write/destructive/idempotent, so the bar is lower; the description adds real context by explaining the impact ('changes what Bsale charges on new sales') and clarifying the price is tax-exclusive. It doesn't mention permission or reversal semantics, keeping it at 4.

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?

Front-loads 'WRITE:' then the operation, impact, prerequisite, and endpoint in three tight sentences with no waste.

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 3-param mutation with no output schema and safety covered by annotations, the description supplies the mutation subject, impact, prerequisite, and endpoint. It is essentially complete, with only a minor gap on price_list_id semantics.

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 description clarifies net_price is tax-exclusive and directs where detail_id comes from, adding meaning beyond the 67%-covered schema. price_list_id is left to the URL pattern rather than described, so not a perfect 5.

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?

States a specific verb and resource: 'set the net price ... of one variant in a price list'. It distinguishes the operation clearly from sibling reads and other update tools, and even names the exact field (variantValue) being changed.

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?

Explicitly routes the agent to bsale_list_price_list_details to obtain detail_id, which is the key prerequisite. It does not discuss when-not-to-use or alternatives for the update itself, but the operational context is clear.

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