MolTrust

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

Excellent disclosure of return values (wallet address, contract, conversion rate, instructions) compensating for absent annotations; no side effects mentioned but implied by info-only nature.

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?

Optimal two-sentence structure front-loaded with verb; every sentence conveys distinct information (purpose then return values).

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?

Sufficient for complexity level; describes return values adequately given output schema exists, though could mention this is read-only/preparation step.

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?

Baseline score for zero-parameter tool; no parameters require semantic explanation.

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?

Clear specific action (Get USDC deposit instructions) and resource (MolTrust credits), but lacks explicit differentiation from sibling 'moltrust_claim_deposit'.

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 on when to use versus alternatives like 'moltrust_claim_deposit' or 'moltrust_credits', nor any exclusion criteria.

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