MolTrust

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

Discloses return values (status, brand info, SKUs, expiry) which is helpful given no annotations exist, but omits error handling, rate limits, or failure modes.

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 specific checks, return values, and parameter details; no redundant sentences.

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?

Adequately complete for a single-parameter tool; covers inputs, processing logic, and return values despite existence of output schema.

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?

Compensates effectively for 0% schema description coverage by providing an Args section with a clear example ('did:web:sneakerstore.com') explaining the expected DID format.

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 verifies reseller authorization via MT Salesguard, specifying it checks if a reseller DID is authorized by a brand to sell products, distinguishing it from the more general mt_salesguard_verify sibling.

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 versus mt_salesguard_register or mt_salesguard_verify, or prerequisites like requiring registration first.

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