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

Annotations already establish readOnly, idempotent, non-destructive, non-open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: that checkout applies location-based tax, that Enterprise contracts are not purchasable through checkout, and precisely what each catalog section contains — valuable given no output schema exists.

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 entire definition is a single sprawling sentence with deeply nested parentheticals that reads like a transcribed response schema. It is dense and poorly front-loaded, forcing the reader to parse clauses rather than grasp the tool's role 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?

With no parameters, no output schema, and annotations covering safety, the description's job is largely to convey what comes back — which it does exhaustively (packs, team.plans, enterprise, limits, trial). It is complete enough to call and interpret, short of explicitly stating its relationship to the checkout tools.

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?

The tool takes zero parameters, so there is no parameter meaning to convey; the 4 baseline applies. The description does not need to compensate for any schema gap here.

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 (list) and resource (SHIP's catalog of credit packs, monthly plans, Enterprise tiers, limits, trial). The scope is unambiguous, though it does little to differentiate itself from sibling list_* tools and reads more like a response inventory than a purpose statement.

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?

No explicit when-to-use, when-not-to-use, or named alternatives. The mention that 'contracts are sold by SHIP, not through checkout' faintly gestures at start_credit_checkout, but the agent is left to infer that this is the read-only catalog-lookup counterpart to the checkout/request_more_credits tools.

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