clob_get_midpoint

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

No annotations are provided, so the description must cover behavioral traits. It notes the input is a single CLOB token ID, but does not disclose what happens if the token is invalid, any side effects, or rate limits. It is adequate for a simple fetch operation.

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 concise with only 5 sentences, directly stating the purpose and usage guidelines. It could be slightly more streamlined but is well-structured and front-loaded.

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 low complexity, single parameter, and presence of an output schema, the description adequately covers when to use it. It does not describe the return value, but that is handled by the output schema.

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 input schema has 100% coverage with one parameter (args.token_id). The description reiterates that it takes a single token ID, adding no new semantic meaning beyond the schema.

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 explicitly states 'Fetch the midpoint for one token', using a specific verb and resource that clearly defines the tool's function. It distinguishes itself from siblings like get_book by focusing on the midpoint rather than the full order book.

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?

X The description provides clear guidance on when to use this tool ('when the user specifically wants the midpoint') and when not to ('if depth matters too, use get_book instead'). It also recommends using it for reasoning about fair value.

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