MolTrust

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

Since no annotations exist, description effectively discloses return payload structure (score, ROI, events) though omits rate limits or error behaviors.

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?

Docstring format is appropriately sized, front-loaded with purpose, and every line provides distinct value (purpose, returns, parameter specs).

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?

Complete for a single-parameter read operation; acknowledges output schema exists by summarizing returns rather than detailing, though could mention error handling.

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?

With 0% schema coverage, description excellently compensates by specifying format (0x-prefixed, 42 chars) and semantics (Prediction market wallet address).

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 'Get' with clear resource 'prediction market profile and track record', distinctly different from sibling leaderboard/link 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 function (individual wallet lookup) but lacks explicit when/when-not guidance vs alternatives like mt_prediction_leaderboard.

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