MolTrust

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

Describes what data is returned, but lacks disclosure of behavioral traits like caching, rate limits, or computational cost since no annotations are provided.

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 two sentences front-loaded with essential information—purpose and return values—no redundant or wasted text.

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 simple getter with no parameters and existing output schema; lists specific statistics returned, though domain context for 'Swarm Intelligence' assumes prior system knowledge.

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?

Baseline score applies as there are zero input parameters; schema is empty and requires no additional semantic explanation.

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 global Swarm Intelligence statistics and enumerates specific return values (agents, endorsements, trust scores), though it could explicitly differentiate from sibling mt_get_swarm_graph.

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 guidance on when to use this versus related tools like mt_get_swarm_graph or mt_get_trust_score, nor any exclusions or alternatives mentioned.

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