MolTrust

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

Discloses the 2-hop traversal limit and return structure (nodes/agents and edges/endorsements), but omits error handling, authentication requirements, or rate limits.

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?

Extremely concise with no redundant information; front-loaded with the core action and brief return value description, followed by the Args specification.

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 an output schema; provides sufficient high-level context about the return structure without needing to replicate the full output schema details.

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 defining 'did' as the 'DID of the agent to get graph for,' clarifying both the data type and semantic purpose.

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 'trust propagation graph' for an agent with specific '2 hops' scope, distinguishing it from siblings like mt_get_trust_score (which returns a scalar score) and mt_endorse_agent (which creates endorsements).

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 no guidance on when to use this versus alternatives like mt_get_trust_score or mt_get_swarm_stats, nor any exclusion criteria.

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