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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only lists returned data types and does not mention that this is a read-only lookup, any rate limits, error cases, or response format. The 'get' name implies read-only, but the description itself adds no explicit behavioral context.

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 terse, which is efficient, but it is a noun-phrase fragment rather than a complete sentence. It conveys the gist in few words but omits important structure such as what the tool does (returns) and the parameter semantics, so it is more under-specified than properly 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 tool with two required parameters and no output schema or annotations, this description is too thin. An agent lacks guidance on valid parameter values, how the returned data is structured, and how this tool relates to siblings such as get_index. The description does not provide enough context for reliable invocation.

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 0%, so the description must compensate. It mentions 'task class' and 'model', which map to the two required parameters, but it does not explain what valid values look like, what 'task class' means, or how model names should be formatted. This is minimal value beyond the raw parameter names.

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 specifies the resource ('SIU price, exchange rate and index refs') and the scope ('for one task class and model'), so an agent can infer that get_quote returns quote-related data. It lacks an explicit verb, and 'index refs' overlaps with sibling get_index, so it does not fully distinguish itself from 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?

The description gives no guidance on when to use get_quote versus alternatives like convert or get_index. It only states the input scope, leaving the selection logic entirely to the agent.

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