company_price_catalog

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

With no annotations present, the description carries the full burden. It hints at both read ('Inspect') and write ('advance') behavior but does not disclose side effects, reversibility, required permissions, or what 'verified receipts' refers to. An agent cannot tell whether 'advance' mutates state or what consequences that has.

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, short sentence, which is superficially concise. But it is overloaded with unexplained jargon ('scoped chain lifecycle', 'verified receipts') and fails to front-load any actionable information. Every clause raises more questions than it answers.

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 tool with seven parameters, no annotations, and no parameter descriptions, a single vague sentence is grossly incomplete. While an output schema exists, it does not compensate for missing behavioral and invocation guidance. An agent would be unable to correctly construct a call or know what operation values are valid.

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 0% – none of the seven parameters are described in the schema. The description adds no meaning to any parameter: it does not explain what 'project_id', 'bundle_json', 'operation', 'payload_json', or the others are for. The default 'operation' value of 'list' is a critical behavioral hint that is entirely absent from the description.

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 names a specific resource ('price catalog versions') and gives two verbs ('Inspect' and 'advance'), so the basic purpose is present. However, the phrases 'scoped chain lifecycle' and 'verified receipts' are vague and unglossed, leaving the exact scope of 'advance' unclear. It does not meaningfully distinguish this tool from nearby siblings like 'company_price_book' or 'company_price_probes'.

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?

There is no guidance on when to use this tool versus alternatives, no mention of common scenarios, and no exclusions or preconditions. The description's 'through the scoped chain lifecycle' implies a specific workflow, but it never states what triggers an 'inspect' versus an 'advance'.

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