MolTrust

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

Lacking annotations, the description carries the burden but only discloses return data structure; omits auth requirements, rate limits, cache behavior, or cost implications of querying network-wide statistics.

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?

Appropriately brief two-sentence structure front-loads the action ('Get') and follows with specific return values, though the null title wastes an opportunity for additional context.

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?

Sufficient for a zero-parameter tool with an output schema; describes the category of returned data (network health metrics) without needing to detail individual fields.

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?

Input schema has zero parameters, warranting the baseline score; description correctly implies no filtering is needed for these global aggregate metrics.

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 MolTrust network statistics and specifies aggregated metrics returned (agents, credentials, ratings), distinguishing it from action-oriented sibling tools like moltrust_register or moltrust_rate.

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 sibling query tools like moltrust_reputation or moltrust_credits, or what analytical questions it answers best.

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