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

With no annotations, the description must carry behavioral disclosure. It adds meaningful context: this is an upsert-style save, scoped to owner or office, and does not automatically populate quotes. However, it does not describe permissions, reversibility, partial-update behavior, or side effects such as category creation.

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 two efficient sentences with the core action and update condition front-loaded. Every sentence adds useful context without repetition or filler.

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?

This is a 16-parameter mutation tool with no annotations and no output schema. The description gives the basic save/update condition and item purpose, but it does not cover permissions, response behavior, or important side effects for tasks, categories, and pricing fields. For this complexity, it leaves significant contextual 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 description coverage is moderate at 69%, so the schema already documents many parameters. The description adds useful meaning for item_id by indicating it switches the operation from add to change. Most other parameter semantics, such as parts, task_code, cost, markup, and member pricing, are left to the schema.

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 states a specific verb and resource: add or change a price book item. It also clarifies the conditional update path via item_id. It does not explicitly differentiate from siblings such as pricebook_archiveItem or pricebook_taskCost, but the save/upsert purpose is still clear.

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?

It explicitly says to add when no item_id is given and to change when item_id is present. It also gives useful context that items are a pick list for quote lines and are never auto-filled. No alternative sibling tool is named, but the core usage condition is clear.

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