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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the useful 'Free' cost signal but does not go further to explain whether authentication is needed or how the endpoint behaves; there is no contradiction with annotations.

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 extremely short and front-loads the important pricing categories before the 'Free' note; there is no filler. It is structured as fragments rather than a full sentence with an explicit verb, which slightly weakens clarity but keeps it concise.

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 simple read-only endpoint with one optional parameter and an output schema, the key contents are listed. However, the description omits any statement of what operation the tool performs or when to choose it over the nearby estimate_lowpoly_cost and get_lowpoly_model endpoints, leaving part of the selection context to inference.

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 single optional rd_api_key parameter is fully documented in the schema (100% coverage), so the description does not need to explain it. The description adds no parameter-level detail, but the baseline of 3 is appropriate because the schema carries the full burden.

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 identifies a concrete resource — Low-Poly pricing — and enumerates the specific contents (sizes, per-operation prices for generate/revise/animate, styles, limits, export targets), so an agent can tell this is the pricing/metadata endpoint. It lacks an explicit verb such as 'retrieves' or 'returns,' and it does not directly differentiate from sibling estimation tools like estimate_lowpoly_cost, stopping short of a 5.

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 guidance is given on when to call this tool versus estimate_lowpoly_cost, get_balance, or the low-poly job/model getters. The only usage hint is 'Free,' which says the call itself has no cost but does not state when this endpoint is the right choice or when an alternative should be used.

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