sf_pricebook_entries

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description reinforces this with '[READ-ONLY]' and adds context about the data model (price book entries define prices in specific contexts). 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 mostly concise but has slight repetition: the first sentence states 'Retrieves PricebookEntry records' and the later sentence says 'Get all product price entries'. Useful markers like [INSTRUCTIONS] and [READ-ONLY] help structure.

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?

No output schema exists, but the description lists returned fields (product name, code, unit price, currency, active status). It explains the concept of price book entries. Minor inconsistency: says 'Get all product price entries' but a limit parameter exists, potentially confusing.

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% and already fully describes parameters (pricebookId with format hint, limit with default). The description does not add extra details beyond what the schema provides, so 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 it retrieves PricebookEntry records for a specific price book, listing the fields returned. It distinguishes from sibling tools by focusing on a single price book's entries, while others like sf_list_pricebooks list price books themselves.

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 explicitly advises use cases: check pricing, compare across price books, verify product availability. It also tells how to obtain the required pricebookId via sf_list_pricebooks. No negative guidance, but positive context is strong.

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