catalog_delete_metering_policy_assignment

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is carried structurally. The description adds nothing beyond restating the HTTP DELETE verb — no mention of irreversibility, side effects on related catalog items, or authorization requirements, which is the value it should add for a destructive operation.

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?

Three lines conveying the identical fact — a prose 'Delete the pricing card assignment with specified id', a near-duplicate 'Deletes the pricing card assignment with the specified id', and the raw 'DELETE /price/...' path. Two of the three sentences are pure duplication and the useful routing/impact information is absent.

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 one-parameter delete with full annotation coverage and full schema coverage, the description is minimally adequate: the agent knows it deletes an assignment by id. It is not complete, though — consequences of removal, permission requirements, and the pricing-card vs metering-policy terminology mismatch are all unaddressed.

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 id parameter is documented as the pricing card assignment id (path), so the schema does the work. The description only says 'with specified id' and contributes no format, sourcing, or lookup guidance beyond that — baseline 3.

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 ('Delete the pricing card assignment') and identifies the target by id, so the action is unmistakable. It loses a point because the tool name says 'metering_policy_assignment' while the description repeatedly says 'pricing card assignment', and it never distinguishes itself from siblings like catalog_patch_metering_policy_assignment or catalog_delete_policy.

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 versus catalog_patch_metering_policy_assignment or catalog_get_metering_policy_assignment, no prerequisites, and no note about needed permissions or scope. The only usage signal is the implied 'delete = removal', which an agent must infer.

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