Get Current CoW Auction

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that the tool returns the current auction state (ID, block, orders, prices), providing concrete behavioral expectations beyond the annotation hints. No contradictions.

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 well-structured with a brief introductory line, a contextual sentence, and bullet lists for args and returns. It is concise but includes helpful protocol context; could be slightly trimmed without losing value.

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 tool with one parameter and clear annotations, the description covers the essential return fields. However, it lacks details on potential pagination or limits for orders, and does not mention error cases. Still, it is largely complete.

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 coverage is 100% with a clear description for the parameter. The description merely restates 'network: The blockchain network' and does not add significant new meaning beyond the schema's enum definition and default value.

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 begins with a clear verb-resource statement: 'Get information about the current auction batch.' It distinguishes from sibling tools like cow_get_order (individual order) and cow_get_quote by specifying it returns the batch-level auction state, including orders and prices.

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 implies usage for retrieving the current auction state but does not explicitly state when to prefer this tool over siblings, nor does it mention when not to use it. Some guidance on selecting between auction and order-level tools would improve clarity.

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