MolTrust

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

Discloses return values (evidence_hash, base_tx_hash), anchoring mechanism (Base L2), and expiration behavior, carrying full burden since no annotations exist.

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, followed by behavioral details and parameter definitions; Args section is necessary given schema deficiencies.

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 covers workflow context (prerequisite step) and return values despite existence of output schema; could elaborate on failure modes or hash usage.

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?

Fully compensates for 0% schema description coverage by providing clear semantics for all 5 parameters, including format expectations (DID) and value examples (skill_verification, purchase).

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 (create interaction proof) and target resource (SkillEndorsementCredential), clearly positioning it within the endorsement workflow versus sibling tools.

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?

Explicitly states prerequisite relationship (required before mt_endorse_agent) and temporal constraint (valid for 72 hours), though lacks explicit 'when not to use' guidance.

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