b24_crm_productrows_set

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

Annotations indicate readOnlyHint=false (mutation) and destructiveHint=false (not destructive). The description says 'replace', implying overwriting all product rows, but it does not clarify if the operation clears existing rows first, or if it appends. No mention of auth roles, rate limits, or side effects. With annotations present, the bar is lower, but the description adds minimal behavioral context beyond the basic action.

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 efficiently conveys the core action and scope. No unnecessary words or redundancy. It is front-loaded with the key verb and resource.

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?

The description is minimal but covers the basic purpose. Given the presence of an output schema (not shown but indicated), return values are covered. However, the description leaves ambiguity about behavioral details (like overwriting vs appending) and does not leverage the complex rows parameter to explain how the replacement works practically. Adequate but with gaps.

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 coverage is 100%, with all parameters having descriptions and examples (e.g., rows parameter shows JSON format, owner_type explains 'D', 'L', 'Q'). The description does not add any additional parameter meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 ('replace'), the resource ('product rows'), and the context ('deal/lead/quote'), with the API method in parentheses. It distinguishes the tool from siblings like b24_crm_deal_contacts_set (different resource) and b24_crm_product_list (product catalog), though it does not explicitly differentiate. This gives a clear purpose.

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 provides no information on when to use this tool versus alternatives, nor any prerequisites or exclusion criteria. For a tool that modifies CRM product rows, guidance on when to use b24_crm_product_list for fetching product IDs or b24_crm_deal_contacts_set for contacts would be beneficial, but none is present.

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