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

Annotations only supply destructiveHint=true; the description adds the concrete consequence 'changes what the customer is billed' and the underlying API endpoint, which is useful beyond the hint. However it omits prerequisites, whether an existing plan is replaced or prorated, and any idempotency/permission behavior for a destructive write.

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?

A single front-loaded sentence leading with 'WRITE:' plus a short API reference; every element earns its place and the mutation nature is visible at a glance.

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 destructive write with no output schema, the description covers purpose and impact but leaves prerequisite and side-effect questions (plan replacement semantics, effective-date defaults) unaddressed, so it is adequate rather than 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 description coverage is 100%, so all five parameters (including the optional product_id and start/end times) are already documented in the schema. The description adds no parameter-level detail, 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?

States a specific verb (assign/attach) and resource (pricing product plan to a customer) and immediately conveys the consequence: 'this changes what the customer is billed.' That distinguishes it clearly from the read-oriented siblings like amberflo_get_customer_plan and amberflo_list_customer_plan_history.

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 'WRITE:' prefix hints at the mutation context, but there is no explicit when-to-use guidance or routing to alternatives (e.g., 'use get_customer_plan to inspect the current assignment first'). Nothing tells the agent when this is the right tool versus other plan-related siblings.

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