get_quote

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

With no annotations, the description carries the full burden. It discloses the tool is 'cheap' and performs 'one book fetch', indicating performance characteristics, and specifies exactly which fields are returned (best_bid, best_ask, mid, spread) and that there is no depth. It lacks details on error handling or auth, but for a simple quote tool this is adequate.

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 a single, efficiently structured sentence that front-loads the purpose ('Cheap price check'), then specifies the token scope and available fields. Every phrase earns its place with no waste.

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?

Given the tool's simplicity (1 parameter, no output schema), the description covers what it does, what it returns, and how it works ('one book fetch'). It also hints at its limitation (no depth), making it sufficient for tool selection even with sibling tools present.

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 schema already fully describes token_id as 'CLOB token id for one specific outcome.' The description reinforces this with 'one outcome token' but adds no new syntax or format details. With 100% schema coverage, the baseline of 3 is appropriate.

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 clearly states the tool performs a 'cheap price check for one outcome token' with specific fields (best_bid, best_ask, mid, spread), distinguishing it from siblings like get_order_book which would provide depth.

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 provides clear context by saying 'no depth' and 'only', implying it's for quick checks when full order book depth is unnecessary. However, it does not explicitly name alternatives like get_order_book, so it offers a clear context with an implicit exclusion rather than explicit alternatives.

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