MolTrust

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

Discloses verification mechanism (checks ProductProvenanceCredential from authorized brands) and specific return values (brand info, credential hash, Base anchor, risk level) despite no annotations.

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?

Compact, front-loaded structure with no filler; efficiently covers purpose, mechanism, returns, and parameter in four 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?

Adequate for single-parameter tool with output schema; mentions credential type and return fields, though could note error conditions or authorization edge cases.

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 for 0% schema description coverage by providing concrete example (AIRMAX-90-WHITE-43) that clarifies expected product ID 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?

Clear specific verb (verify) + resource (product provenance via MT Salesguard), distinctly differentiates from siblings like mt_salesguard_register, mt_shopping_verify, and mt_travel_verify.

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?

Usage is implied by specific scope (Salesguard product provenance), but lacks explicit when-to-use guidance or comparisons to similar verification tools like mt_shopping_verify.

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