MolTrust

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

Discloses the 8-point audit scope, SHA-256 hashing, and scoring mechanics (100 base, >=70 passing) despite no annotations.

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?

Front-loaded one-line summary followed by technical details and isolated Args section; every sentence earns its place.

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?

Covers audit methodology and scoring adequately; presence of output schema excuses lack of return value documentation.

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?

Args section compensates for 0% schema description coverage by clarifying github_url accepts GitHub repos or direct HTTPS links to SKILL.md.

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?

Specifically states it audits SKILL.md files for security risks via an 8-point check, clearly distinguishing from sibling credential/issue/verify tools.

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?

Describes what it does but lacks explicit when-to-use guidance or differentiation from mt_skill_issue_vc/verify siblings.

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