prices.deactivate

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It says only 'Deactivate a catalog price' without explaining effects (e.g., irreversible, hides from listings, impacts existing subscriptions), permissions required, or response behavior. This is a significant gap for a mutation tool.

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 clear sentence with no redundant words, making it highly concise. However, its brevity borders on under-specification, preventing a higher score for structure since it lacks any supporting context.

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 mutation tool with no annotations, no output schema, and only partially documented parameters, the description is incomplete. It does not mention side effects, return values, or any prerequisites. The sibling set includes read-only and mutation tools, but this description does not provide enough context to guide safe invocation.

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 50% (only price_id has a description). The tool description adds no parameter semantics, leaving organization_id completely undocumented and not clarifying the format or purpose of price_id beyond its schema description. Since coverage is not high, the description should compensate but does not.

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 uses a specific verb ('Deactivate') and resource ('catalog price'), clearly indicating the action. It distinguishes from sibling tools like prices.create and prices.update by the deactivation intent, though it does not elaborate on scope or nuances.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to use prices.update for reactivation or whether deactivation is only for temporary states. The description is purely a statement of action with no contextual 'when' or 'when not'.

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