catalog_change_metering_assignment_strategy

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

Annotations already declare non-readOnly, non-idempotent, non-destructive, open-world, so the safety profile is covered. The description adds the org-wide scope ('for the Org') which is genuinely useful, but says nothing about what happens to existing per-entity assignments, reversibility, or permissions required for a private admin endpoint.

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?

Two short lines with the verb-led purpose front-loaded; nothing is padded. The raw PATCH path is marginally useful for tracing the endpoint but is thin filler compared to what an agent actually needs.

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?

A one-parameter mutation with full schema coverage and annotations does not need much, but for a private org-level strategy override the description should note the effect of choosing ALL vs PROJECT vs CLOUDZONE and whether the change is global. Those omissions leave it only adequate.

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 100% and the schema already documents the single 'body' object and the entityType enum (ALL/PROJECT/CLOUDZONE), so the description need not repeat it. It adds no syntax, default, or semantics beyond the schema — baseline 3 applies.

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?

States a specific verb ('Updates') and resource ('pricing card assignment strategy') scoped to the Org, which is clearer than the name alone. However it does not disambiguate from the sibling pair catalog_create_metering_assignment_strategy and catalog_get_metering_assignment_strategy, so an agent could confuse 'update' with 'create' on a similar-looking metering-strategy resource.

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 statement of when this should be chosen over the create or get variants, nor any prerequisite (e.g. that a strategy must already exist to patch). The only context is the raw PATCH path, which implicitly says 'mutate existing' but requires inference.

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