catalog_patch_metering_policy_assignment

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

The description does surface a real side effect: a body with entityType=ALL deletes the older assignments for the given pricingCardId. However, annotations declare destructiveHint=false, so the two signals cannot both be trusted; the deletion behavior is exactly the kind of thing an agent needs before calling a PATCH. Idempotency and authorization requirements are still unaddressed.

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 sentences plus a raw path, front-loaded and free of padding. The first sentence is circular ('updates the assignment id with the supplied id') and the raw HTTP path is redundant with the title, so a bit of the text does not earn its place.

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 2-parameter mutation with a fully described nested body and no output schema, the description covers the essential side effect but omits permissions, whether the addressed assignment is replaced in place, and what the PATCH returns. Adequate, not complete.

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 goes beyond the schema by explaining the semantic consequence of the entityType=ALL enum value, which the schema only labels as 'Pricing card assigned entity type'. That is real added meaning for the nested body parameter.

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 ('Updates the pricing card assignment id') and appends the raw PATCH path, so an agent can tell this is a mutation of an existing pricing-card assignment rather than a create/delete. It does not explicitly differentiate itself from the adjacent catalog_create_metering_policy_assignment / catalog_delete_metering_policy_assignment siblings, but the verb does the work implicitly.

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 statement of when to use this over catalog_create_metering_policy_assignment, catalog_change_metering_assignment_strategy, or catalog_delete_metering_policy_assignment, and no preconditions (e.g. the assignment must already exist). The only conditional guidance is an implied side-effect of entityType=ALL, not a usage rule.

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