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

The description's only behavioral claim is 'no execution', i.e. a side-effect-free quote, while the annotations declare readOnlyHint=false. That is a direct conflict about whether this tool has side effects. The rest of the behavioral profile (openWorldHint=true, idempotentHint=false) is carried entirely by annotations, and the description adds no context such as whether quoting consumes points or requires auth.

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?

Extremely short, but the brevity is under-specification rather than concision: the single fragment is verbatim the tool title and carries no front-loaded guidance about scope, inputs, or output. Nothing is wasted, but almost nothing is communicated.

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 five optional parameters, a nested object, zero required fields, and no output schema, the description should explain what a quote returns and how endpoint/tier/asset shape it. It supplies only 'points a call would cost, no execution', leaving the agent to guess the return shape and the meaning of the nested models map.

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 tier, asset, agents, models, and endpoint are already documented in the schema, including the nested agent->model_id object. The description adds nothing about any of them, so the baseline 3 for high-coverage schemas applies.

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?

Tautological: description restates name/title.

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?

There is no statement of when to use this versus pricing_get, usage_get, or the run/start execution siblings; the 'no execution' note only hints that it precedes an execution call. No prerequisites, no when-not-to-use, no named alternative.

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