agentek-eth

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

With no annotations provided, the description carries full burden. It mentions fetching 'latest state' which implies read-only behavior, but doesn't disclose important behavioral traits like whether this requires authentication, rate limits, error conditions, response format, or if it's a real-time query versus cached data.

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?

Single sentence that efficiently conveys the core purpose. No wasted words or unnecessary elaboration. The structure is front-loaded with the main action and immediately specifies what information is included.

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 no annotations, 0% schema description coverage, and no output schema, the description is inadequate. It doesn't explain the single required parameter, doesn't describe the return format, and provides minimal behavioral context. Given the complexity of DeFi pool data, more guidance is needed.

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 doesn't mention the 'poolId' parameter at all, nor provide any context about what format it expects or where to obtain valid pool IDs. The baseline would be lower, but with only 1 parameter, some understanding can be inferred from context.

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 action ('Fetch') and resource ('pool'), specifying what information is retrieved ('latest state, including reserves and price information'). It distinguishes from some siblings like 'getUniV3Pool' by being generic, but doesn't explicitly differentiate from all pool-related tools.

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?

No guidance on when to use this tool versus alternatives like 'getUniV3Pool' or 'getPoolFeeData'. The description implies it's for retrieving pool state, but provides no context about prerequisites, limitations, or when other tools might be more appropriate.

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