base_price

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

No annotations are provided, so the description carries full behavioral disclosure burden. It does not mention data source, freshness, rate limits, or what 'current' means (e.g., latest block, live feed). The description only states the basic action without any behavioral nuance.

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?

A single, front-loaded sentence conveys the tool's purpose with no unnecessary words. It is concise and easy to parse.

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 price tool, the description is minimally viable, but lacks behavioral context and parameter semantics. An output schema exists, which may cover return values, but it is not referenced in the description. Given no annotations, the description is not fully complete for selecting and invoking the tool confidently.

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%, and the description does not elaborate on the 'token' parameter beyond its name. The default 'ETH' appears in the schema, but the description adds no format, supported values, or examples, so agents must guess what tokens are accepted.

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 'Get current price of a token on Base L2' clearly identifies the action (get price) and resource (token on Base L2), and differentiates it from sibling tools like base_gas_estimate (gas) and dex_quote (quotes for trades).

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 explicit when-to-use or alternative guidance, but the context is clear: use this tool when you need a token's current price. It does not mention exclusions or alternatives, so it falls into implied usage rather than explicit guidance.

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