update_proposal_pricetables

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

The annotations already flag destructive=true, idempotent=true and openWorld=true. The description adds the crucial detail behind that destructive flag: rows of named tables are wholesale replaced rather than merged, while unnamed tables are untouched. It also discloses the return payload (updated tables plus proposal total), which no output schema provides.

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?

Three short sentences: the action first, the scope caveat second, the return value last. Nothing is redundant and nothing important is buried.

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 destructive write with a deeply nested row schema and no output schema, the definition covers the top-level contract (replace semantics, scope, return value) but leaves the caller guessing about row field requirements and null handling on replacement. Adequate but with a meaningful gap.

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 0%, so the description must compensate and it largely does not. It hints that 'pricetables' carries table ids and row data, but says nothing about the many row fields (sku, price, quantity, discount_type, discount_value, recurring_type, vat_percentage, hide_* flags) or about whether omitted optional fields are nulled out during the full replacement.

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: 'Replace all rows of the named price tables in a proposal.' That clearly separates it from the read-only siblings (get_proposal_details, search_proposals) and from create/copy/send proposal tools. It stops short of naming an alternative for partial row edits, which is why it is not 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?

'Tables that are not named stay unchanged' implies partial-update usage and is a useful scoping cue. There is no explicit when-to-use/when-not-to-use guidance, no prerequisite that proposal_id must reference an existing proposal, and no mention of what to do if a table id does not exist.

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