MolTrust

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

No annotations provided; description compensates by explaining cryptographic signing, enforced segment permissions, spend limits, and validity periods, though omits operational details like costs or prerequisites.

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 clear opening summary followed by Args section; every sentence provides 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?

Comprehensive coverage of all 7 parameters with defaults/optionality noted; output schema exists so return value explanation is unnecessary.

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 has 0% description coverage; description fully compensates with detailed Args section including examples (e.g., 'did:base:0x...', 'hotel,flight,car_rental') and semantics (e.g., 'Maximum spend amount per booking').

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?

Explicitly states it issues a TravelAgentCredential for booking agents, distinguishes from siblings via travel-specific details (hotel/flight/car_rental segments) and cryptographic authorization features.

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?

Implies usage through domain-specific terms (travel, booking) but lacks explicit when-to-use guidance versus siblings like mt_shopping_issue_vc or mt_skill_issue_vc.

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