catalog_get_metering_policy_assignment

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and even repeat the endpoint path, so the safety profile is fully covered without the prose. The description's one addition is the "private cloud" scope, which hints at a distinct endpoint family, but it says nothing about the response shape or what happens on an unknown id.

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 same fact is restated three times in three lines ("Fetch pricing card assignment... by id", "Returns a pricing card assignments by id", and the raw path). Only the first line carries information; the rest is duplication that dilutes rather than front-loads.

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 read tool with full schema coverage and complete annotations, the minimum is met. However, with no output schema there is no statement of what a pricing card assignment contains or how an empty/missing assignment is surfaced, which is the remaining gap an agent would want closed.

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% and the single 'id' parameter is already documented as a UUID path parameter in the schema. The description only echoes "by id" and adds no format, sourcing, or lookup guidance beyond the schema, so the 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?

The description states a specific verb ("Fetch") and resource ("pricing card assignment for private cloud by id"), and the singular-by-id framing separates it from list siblings such as catalog_get_all_metering_policy_assignments. The only friction is the terminology drift between the tool name ("metering_policy_assignment") and the description ("pricing card assignment"), which an agent must infer are the same object.

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_get_all_metering_policy_assignments, catalog_get_metering_assignment_strategy, or catalog_patch_metering_policy_assignment. The agent must infer from the tool name alone that this is the single-record read.

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