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

Annotations already declare readOnlyHint and non-destructive behavior, and the description adds meaningful behavioral context: paid products debit a prepaid credit key and are never charged on failure. It also discloses the broad product coverage, which helps the agent predict what kind of data will be returned.

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 description is front-loaded with the main action and routes the call after catalog lookup. The domain list and billing note are long but earned, since they tell the agent what to expect and what a paid call may cost.

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 generic accessor with 133 possible products, the description covers the full call cycle: lookup, constructing the request, locating schemas, and billing behavior. An output schema exists for the response, so the lack of an explicit return-format description is not a gap.

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?

With 0% schema description coverage, the description compensates by showing the exact JSON shape (product_id plus params), explaining that product_id comes from the catalog search, and pointing to the catalog entry for each product's input and output schema. It does not enumerate every param, but that is delegated appropriately to the catalog.

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 uses a specific verb ('RUN ANY ... by id') and a concrete resource ('the 133 AnswerPool products'), and immediately distinguishes this accessor from answerpool_search_catalog by describing it as the main execution path after lookup. This makes the tool's purpose unmistakable relative to its siblings.

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?

It gives an explicit workflow: find an id with answerpool_search_catalog, then pass the product inputs as a JSON object, with a concrete example. It does not spell out negative exclusions for other siblings, so it stops short of a full when-not-to-use statement.

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