MolTrust

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

Discloses specific validation checks performed (signature, spend limits, trust score) and return type (verification receipt), which is critical given no 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?

Well-structured with purpose up front and Args section providing necessary parameter semantics; no extraneous content.

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?

Adequate for moderate complexity; mentions return receipt type and validation criteria without needing to detail output schema fields.

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?

Excellent compensation for 0% schema coverage by providing JWS format details, currency examples (USDC), and amount formatting (189.99).

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 verb ('Verify') and resource ('shopping transaction against a BuyerAgentCredential'), though could better distinguish from mt_salesguard_verify.

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 mt_shopping_issue_vc or mt_salesguard_verify, or when verification might fail.

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