Create Price Book

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

While annotations already indicate this is a write operation and not idempotent, the description adds meaningful behavioral context: it can also create PricebookEntry records and that isStandard 'true only for the standard price book'. This goes beyond the structured annotations without contradicting them.

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 front-loaded with the core purpose and then gives background and a compact parameter list. There is minor redundancy with the schema's parameter descriptions, but the structure is clear and each section serves a purpose.

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 create tool with no output schema, the description covers the main action, optional sub-actions, and key constraints. It lacks details on potential errors or prerequisites (e.g., existing products), but acceptable given the tool's moderate complexity and absence of an output schema.

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%, so the baseline is 3, but the description adds extra semantic value. For instance, it clarifies that isStandard is 'true only for the standard price book' and that products is an 'optional array of {productId, unitPrice, useStandardPrice?}' to add to the price book, enriching the parameter definitions.

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 'Creates a Pricebook2 record and optionally adds products with pricing via PricebookEntry records,' using a specific verb and resource. It distinguishes itself from sibling create_* tools by focusing on Pricebook2 and its optional related 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 provides clear context on when to use the tool: 'Price books define the prices for your products' and mentions standard vs. custom price books for customer segments/regions. However, it does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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