MolTrust

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

Discloses analysis methodology (volume spikes, price-volume divergence, liquidity ratios) but lacks information on side effects, auth requirements, or rate limits since 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 front-loaded purpose statement, specific technical details, and Args section; no redundant sentences despite brevity.

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?

Adequately covers the simple single-parameter input and analytical purpose; omits return value explanation appropriately since output schema exists.

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 'Polymarket market/condition ID' in Args section, clarifying both the domain and acceptable ID formats.

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?

States specific action (check/analyzes) and resource (Polymarket) with clear focus on integrity anomalies, distinguishing from sibling tools like moltguard_detail or moltguard_score.

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?

No explicit guidance on when to use vs alternatives (e.g., when to use this instead of moltguard_detail) or exclusion criteria.

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