MolTrust

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

Discloses data sources (Blockscout, ERC-8004, MolTrust) but omits operational details like rate limits, caching behavior, or authentication requirements given 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, return value summary second, and parameter details in Args section; no extraneous 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?

Adequate for a single-parameter tool with output schema; lists key return components without needing to fully describe the output structure.

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?

Effectively compensates for 0% schema description coverage by specifying the address is a Base (EVM) wallet with 0x prefix format in the Args section.

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 retrieves a detailed agent trust report and distinguishes from siblings by listing specific components (Blockscout history, ERC-8004, MolTrust DID, Sybil indicators) that imply comprehensive depth vs other moltguard_* 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?

Implied usage through emphasis on 'detailed' and component list, but lacks explicit guidance on when to choose this over siblings like moltguard_score or moltguard_sybil.

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