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

Adds substantial context beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false): explicit payment requirement, MAT-only balance, current disabled-billing state, and the 429 behavior once the shared crawl allowance is exceeded. This is exactly the kind of operational context annotations cannot express.

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?

Front-loads the offer, price and validity, then layers caveats, which is the right ordering. It is somewhat sprawling, however: the crawler-family allowance and 429 details read as api_access behavior rather than this purchase tool's, adding length that does not serve the buying decision.

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 everything an agent needs before calling: price and duration, required payment, required pass format, current unavailability, rate-limit consequences, and the separation of MAT allowance from other indexes. With no output schema, the remaining gap (return payload shape) is minor for a purchase endpoint.

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 the schema already documents payment, api_pass, transaction and credit_token in detail. The description only restates the mat_ prefix and MAT-only rule that the api_pass schema field already contains, adding no new parameter semantics. Baseline 3 is appropriate.

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 precise verb+resource with concrete terms: 'Buy 1,000 basic data reads for US$1, valid for 30 days.' It also carves out what this tool is not for ('Catalog discovery and ordinary browsing are free'), separating it from api_access and the free-browsing path without requiring schema inspection.

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?

Gives clear usage context: free operations are called out, payment must be explicit, and it warns that 'Billing is off for now: there is no package to buy,' which effectively tells the agent not to invoke it. It stops short of naming a specific sibling (api_access, pricing, billing) as the alternative path.

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