agentek-eth

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('Get information') without detailing response format, error conditions, rate limits, or authentication needs. This is inadequate for a tool that likely returns complex blockchain 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?

The description is a single, efficient sentence with no wasted words. It is front-loaded and directly states the tool's purpose, 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 the complexity of blockchain data, no annotations, no output schema, and incomplete parameter documentation, the description is insufficient. It does not explain what information is returned, how to interpret results, or handle edge cases, leaving significant gaps for the agent.

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 50%, with 'chain' well-documented but 'blockNumberOrHash' lacking a description. The tool description does not add any parameter details beyond the schema, failing to compensate for the coverage gap. However, the schema provides some clarity, so a baseline score of 3 is appropriate.

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 information about a specific block' clearly states the verb ('Get') and resource ('block'), making the purpose understandable. However, it lacks specificity about what information is retrieved (e.g., block details, transactions, timestamps) and does not differentiate from sibling tools like 'getBlock' or 'getBlockTransactions', leaving ambiguity in scope.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or compare it to sibling tools such as 'getBlock' or 'getBlockTransactions', leaving the agent without direction on tool selection.

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