MolTrust

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

Identifies the on-chain context (Base blockchain, ERC-8004 standard) but omits rate limits, authentication requirements, or details on what 'well-known' action returns.

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 structured Args documentation; concise with no redundant text, though 'Args' formatting is slightly raw.

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 moderate complexity given the output schema exists, but incomplete regarding the 'well-known' action's specific behavior and return 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 documenting conditional requirements (did for 'card', agent_id for 'resolve') with concrete examples 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 queries the ERC-8004 registry on Base to resolve agents, fetch Agent Cards, or look up by agentId, distinguishing it from sibling verification/credential 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?

Explains the three action types and their required parameters, but lacks explicit guidance on when to use this versus sibling tools like moltrust_verify or moltrust_reputation.

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