approve_moolah_proxy

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

The description clearly explains the behavior beyond annotations: it details the two approval modes (exact vs. max) and their consequences, including the risk of unlimited spending. It also specifies that the tool writes transaction data (implied by 'approve' and not read-only). No contradiction with annotations.

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 concise (few sentences), front-loaded with the core purpose, and each sentence adds unique guidance. It does not waste words.

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?

The description covers the purpose and usage well but does not mention the output (e.g., transaction hash) or prerequisites (e.g., wallet must be connected). Given the tool's complexity (blockchain approval), the description could be more complete by explaining the expected result and any necessary prior actions. However, the high schema coverage and annotations partially compensate.

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 schema covers all parameters with descriptions (100% coverage). The tool description adds extra context for the 'amount' parameter, specifying when to use exact vs. max and the associated risks, which enhances semantic understanding beyond the schema's pattern and description. For other parameters, the description doesn't add new info, but the schema is sufficient.

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 (approve TRC20 token spending), the target (Moolah core contract), and the context (before supplying collateral or repaying). It also explicitly notes it's not needed for TRX operations, distinguishing it from other operations. Given sibling tools have different approval targets, this description effectively differentiates.

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 explicitly states when to use the tool (before supplying collateral or repaying), what amount to pass (exact recommended, 'max' only with explicit user opt-in), and what not to use it for (TRX operations). This provides clear decision guidance for the AI agent.

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