catalog_create_metering_assignment_strategy

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the mutation profile is covered. The description adds that fields are validated against business rules (implying request rejection on invalid input) and the one-per-org uniqueness constraint, which is useful non-obvious behavior for a non-idempotent create – but says nothing about failure modes, permissions, or the truncation-hidden content.

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 text opens with a malformed, ellipsis-truncated sentence before the useful sentence, and then repeats the tool's own name inside the description plus a raw endpoint path that the annotations title already carries. Front-loading is poor: the load-bearing statement arrives second.

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 non-idempotent create that validates business rules on a nested body, the description is truncated and leaves key questions open – what validation rules apply, what happens on conflict with an existing strategy, and what the response returns (no output schema exists). The visible text signals the gaps rather than filling them.

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% with a single nested body param, so the baseline is 3. The description restates two of the three allowed entityType values (PROJECT, CLOUDZONE) and omits ALL, so it does not add meaning beyond the schema and is even slightly incomplete relative to the enum.

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 second sentence names a concrete verb and resource ("Create a new pricing card assignment strategy") and adds the REST endpoint, so the intent is recoverable. However, the opening sentence is garbled and mid-sentence truncated, and it never contrasts with close siblings such as catalog_get_metering_assignment_strategy or catalog_change_metering_assignment_strategy, leaving the agent to infer that this is strictly a POST-create.

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?

The "only one strategy for a given org at a given point of time" rule is a real precondition that tells an agent an existing strategy must be changed rather than created again. But it is phrased as a business fact, not as explicit when-to-use/when-to-use-instead guidance, and no alternative tool is named.

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