supply

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

Discloses side effects: requires PRIVATE_KEY and may auto-approve token spending. Since no annotations are provided, description carries full burden and does so adequately.

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?

Three concise sentences, front-loaded with primary purpose. Every sentence adds value without redundancy.

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 deposit tool with two well-described parameters, the description covers function, prerequisite, and automatic behavior, making it complete for an AI 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 coverage is 100%; description adds that amount is in 'human units' (e.g., '1.5' for 1.5 WETH), clarifying format beyond schema.

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?

Clearly states 'Supply (deposit) an asset to Tydro to earn interest.' with specific verb and resource, and is distinguishable from siblings like borrow, withdraw, etc.

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?

Specifies requirement for PRIVATE_KEY env var and mentions automatic approval, providing context for usage. Does not explicitly state alternatives or when not to use, but the function is well-defined.

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