MolTrust

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

Discloses analysis methodology (wallet age, transaction patterns, counterparty diversity, funding clusters) and detection logic (funder→many wallets indicates Sybil ring) beyond empty 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?

Front-loaded purpose statement followed by analysis details; Args section provides necessary schema compensation without excess verbosity.

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; explains input semantics and analysis behavior while output schema handles return value documentation.

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 specifying chain (Base/EVM) and format (0x...) for the address parameter.

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?

Specific verb 'scan' + resource 'Base wallet' + clear Sybil detection focus distinguishes it from sibling credential/score 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?

Implies usage through specific purpose description but lacks explicit when-to-use/when-not-to-use guidance versus alternatives like moltguard_score.

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