MolTrust

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

Discloses significant side effects (DID creation, credential issuance, blockchain anchoring) that have security and identity implications beyond the function name.

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?

Front-loaded with purpose, followed by technical details and parameters; the 'Args:' format is slightly informal but efficiently structured with 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 basic invocation but omits operational context like deposit requirements, gas fees, or error conditions despite the complexity of blockchain anchoring.

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 character constraints, valid character sets, and concrete examples for both parameters 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?

Clearly states it registers an AI agent with specific technical actions (creates DID, issues W3C VC, anchors on Base blockchain), distinguishing it from sibling tools through technical specificity.

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?

Provides no guidance on when to use this tool versus alternatives like mt_register_seed or prerequisites for registration.

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