MolTrust

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

Discloses critical behaviors absent from annotations: security audit threshold (>=70), Ed25519 signing with JWS, and x402 payment requirement ($5 USDC when paywall active).

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, logical flow (process → conditions → payment → parameters), and no redundant information.

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 complex workflow (fetching, auditing, conditional issuance, signing) without needing to explain return values 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 defining author_did with example format and clarifying repository_url accepts either repository URL or direct SKILL.md link.

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 'Issue' with clear resource 'VerifiedSkillCredential for AI agent skill' distinguishes from siblings like mt_skill_audit (audit only) and mt_issue_badge (different credential type).

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 workflow description (audit → issue if score >=70) and payment requirement, but lacks explicit 'when to use vs mt_skill_audit' guidance.

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