sf_list_pricebooks

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's addition of 'READ-ONLY' is redundant but consistent. The description adds context about the standard price book and the purpose of additional price books, which is helpful beyond annotations. No contradictions.

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 structured with an initial instruction block and a summary. It is somewhat verbose but front-loads key information. Every sentence adds value, though could be slightly shorter.

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 tool's simplicity (single optional parameter, no output schema), the description covers its purpose, fields returned, and usage context thoroughly. It explains the significance of the standard price book and use cases for additional price books, making it complete for an AI agent.

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 only parameter is 'limit', which is fully described in the schema (maximum results, default 20). The description does not add any additional meaning or constraints to this parameter. With 100% schema coverage, baseline 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 tool retrieves Pricebook2 records, lists specific fields (name, description, active status, IsStandard), and explains the concept of standard vs. additional price books. It distinguishes from sibling tool sf_pricebook_entries by implying this tool is for price book records themselves, not entries.

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 advises using the tool to find price book IDs before viewing entries, providing a clear use case. However, it does not explicitly state when not to use this tool or contrast with other siblings like sf_products_by_family. The guidance is present but not exhaustive.

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