MolTrust

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

Discloses detailed internal verification pipeline (VC signature, spend limits, delegation chain, etc.) providing transparency into validation logic beyond simple 'verify' label.

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; 10-step list is verbose but adds necessary behavioral detail; Args section efficiently compensates for schema gaps.

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 given complexity: documents all parameters sufficiently, mentions output schema exists so return value description unnecessary, though could note idempotency/read-only nature.

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?

With 0% schema description coverage, the Args section provides critical semantic context including data types, formats (DID, JSON), and valid enum values for all 6 parameters.

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?

States specific action (verify) and target (travel booking against TravelAgentCredential), with detailed 10-step pipeline distinguishing it from issuance siblings.

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 explicit guidance on when to use verification versus issuance (mt_travel_issue_vc) or info retrieval (mt_travel_info); agent must infer from verb.

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