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

The description adds provenance (Stripe webhook, rightsize apply job) and API mirroring, which is useful beyond the read-only/idempotent annotations. It does not mention pagination behavior, default time range, or auth requirements.

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 tight sentences with the core purpose front-loaded. The analogue and endpoint reference earn their place; no filler.

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?

Covers provenance and API mirror but, with no output schema, does not describe returned fields, sorting, or default window. Adequate for a simple list tool but not fully 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 low, so the description must compensate. It helps contextualize 'source' and 'change_type' (plan/price changes from Stripe/rightsize), but it does not clarify 'from', 'to', 'limit', or 'business_id' semantics.

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?

Uses a specific verb ('List') and resource ('plan/price change history'), and immediately distinguishes it as the billing analogue of admin change history. An agent can tell exactly what this tool does.

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?

Explains this is the billing counterpart to admin change history and mirrors a REST endpoint, giving clear context for when it applies. It stops short of explicitly stating when not to use it or naming a preferred sibling for non-billing cases.

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