MolTrust

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

Provides conversion rate (1 USDC = 100 credits) and verification method ('on-chain') absent from annotations, though omits idempotency or failure modes.

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?

Well-structured with purpose front-loaded; Args section effectively substitutes for missing schema descriptions despite unconventional formatting.

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?

Sufficiently complete given output schema exists (no return value explanation needed); conversion details and L2 specificity add necessary context.

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?

Fully compensates for 0% schema description coverage by defining 'tx_hash' format (0x...) and 'did' purpose ('agent's DID to credit') in the Args section.

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?

Specific verb ('Claim') + resource ('MolTrust credits') + source ('USDC deposit on Base') clearly distinguishes this from sibling deposit/info tools.

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?

Describes the workflow sequence (send USDC first, then submit hash) implying when to use, but lacks explicit 'when not to use' or alternative tool references.

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