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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description goes further by disclosing the return payload shape (currentOffers with terms, dates, links) and that links carry the dealer referral code zo=30734402, which an agent would otherwise not know. It stops short of describing pagination or output ordering, which is minor for a static reference tool.

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 primary purpose is front-loaded in the first clause, and the second sentence covers the currentOffers return value without padding. The referral code zo=30734402 is repeated verbatim twice, a small redundancy, and the enum list embedded in prose duplicates the schema.

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 output schema, the description carries responsibility for explaining return values, and it does so for both the account-type explanation and the currentOffers set. The only gap is not clarifying whether 'country' changes offer availability or only link domains, which would matter for US/CA calls.

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%, with 'type' and 'country' both documented and enum-constrained, so the schema does the heavy lifting. The description only reinforces the omit-to-compare behavior already stated in the schema and says nothing about how 'country' affects the returned links or offers, adding little beyond structured fields.

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 names a specific resource (AMSOIL account types) and enumerates exactly what it returns: who each type is for, how types differ, and the enrollment link, plus currentOffers promo codes. This is clearly distinct from siblings like contact_dealer or shop_links, which handle dealer contact and link resolution.

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 description implies usage ('Who each AMSOIL account type is for...') and the schema notes that omitting 'type' compares all types, which is useful call-shaping guidance. However, it never explicitly says when to use this tool versus contact_dealer (for dealer questions) or shop_links (for storefront links), so routing between overlapping siblings is left to inference.

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