MolTrust

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

Adds useful behavioral details (cryptographically signed, enforced spend limits, validity period) but omits side effects like storage location, revocation capability, or computational costs.

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 front-loaded purpose statement followed by behavioral details and structured Args section; no redundant or filler text.

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?

Thoroughly documents all inputs compensating for empty schema; output schema exists so return values need not be described; minor gap regarding credential lifecycle relationship to verification tools.

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?

Comprehensive Args section compensates perfectly for 0% schema description coverage by providing semantics and examples for all 6 parameters including default value for validity_days.

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?

Specific verb (Issue) + resource (BuyerAgentCredential/W3C Verifiable Credential) and distinguishes from siblings (shopping-specific vs travel/skill, and issuing vs verify/info variants).

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 implied usage context (authorizing purchases) but lacks explicit guidance on when to use vs alternatives like mt_shopping_verify or mt_shopping_info.

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