agentek-eth

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

No annotations are provided, so the description carries the full burden. It states it 'Gets' data, implying a read-only operation, but doesn't disclose behavioral traits like rate limits, authentication needs, error conditions, or what the output looks like (no output schema). This is a significant gap for a tool with no annotation coverage.

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, efficient sentence with no wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 no annotations, 0% schema coverage, no output schema, and 2 required parameters, the description is incomplete. It doesn't provide enough context for an AI agent to understand how to invoke the tool correctly or interpret results, especially with many similar sibling tools.

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 mentions 'for a pool' but doesn't explain the parameters 'poolAddress' and 'chainId' (e.g., format of poolAddress, what chainId represents). The description adds minimal value beyond the schema, failing to clarify parameter meanings.

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 'Gets fee-related data for a pool' states a clear verb ('Gets') and resource ('fee-related data for a pool'), but it's vague about what specific fee data is retrieved. It doesn't distinguish from siblings like 'getPool' or 'getUniV3Pool', which might also provide pool-related information.

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 is provided on when to use this tool versus alternatives. With many sibling tools (e.g., 'getPool', 'getUniV3Pool', 'getFeeHistory'), the description lacks context on its specific use case, prerequisites, or exclusions.

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