MolTrust

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

Adds critical behavioral context absent from annotations and schema: public access, no auth requirement, and detailed return value semantics (timing proof, on-chain status, credential type).

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?

Excellent structure with purpose, auth, returns, and args each in distinct segments; no wasted words and appropriately front-loaded.

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 low complexity (single parameter); leverages existence of output schema while still providing helpful context on return values, though explicit sibling workflow mention would improve it.

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 effectively for 0% schema description coverage by specifying the commitment_hash format ('64-char SHA-256'), though it could clarify the hash originates from mt_fantasy_commit.

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 'Verify a fantasy lineup commitment' with specific verb and resource, implicitly distinguishing from sibling 'mt_fantasy_commit' though explicit contrast would strengthen it further.

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 authentication guidance ('Public endpoint, no auth required') but lacks explicit guidance on when to use this versus siblings like mt_fantasy_commit or mt_fantasy_history.

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