MolTrust

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

Discloses critical behavioral details absent from annotations/schema: financial cost ($5/$20), 1-year validity period, and auto-revocation logic if trust score drops.

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 clear front-loading of purpose followed by business logic (tiers/costs) and Args section; every sentence conveys essential information without redundancy.

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?

Comprehensive given the tool's financial/temporal complexity; covers issuance logic, costs, validity constraints, and revocation triggers without needing to detail 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 explaining both parameters (did as 'The DID of the agent', tier with valid values 'verified' or 'trusted') and adding semantic context for tier selection.

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 the specific action (Issue a Verified by MolTrust badge) and target resource, though it doesn't explicitly differentiate from sibling tools like mt_check_badge or mt_get_badge.

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 implicit guidance via tier requirements (score 40+ for verified, 60+ for trusted) but lacks explicit when/when-not rules or comparisons to alternative tools.

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