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 states the tool returns a balance but does not describe error conditions, rate limits, authentication needs, or the format of the return value, which is critical for a read operation with no output schema.

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 zero wasted words. It front-loads the core functionality and avoids redundancy, making it easy for an agent 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?

For a tool with 3 parameters, no annotations, and no output schema, the description is minimally adequate but lacks details on behavioral traits like error handling or return format. It covers the basic purpose but does not fully address the complexity given the missing structured data.

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?

The description adds context by specifying the contract ('Coins contract') and token type ('ERC6909'), which clarifies the purpose of the parameters beyond the schema's descriptions. With 67% schema description coverage, it compensates well for the undocumented aspects, though it could detail parameter interactions more.

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 specific action ('Returns the balance') and resource ('of a given address for a specific ERC6909 token ID from the Coins contract'), distinguishing it from similar sibling tools like getBalance, getBalanceOf, and getAddressCoinBalanceHistory by specifying the exact contract and token type.

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. It does not mention prerequisites like network connectivity or compare it to sibling tools such as getBalance or getAddressTokenBalances, leaving the agent without contextual usage instructions.

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