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

Goes well beyond the annotations: it discloses the URL fetch, SHA-256 hashing, an 8-point check breakdown, a 100-point start with per-finding deductions, and a pass threshold. It stops short of covering failure handling for unreachable/invalid URLs or what the hash is used for downstream, so it is rich but not exhaustive.

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-loads the purpose, then mechanics, then the scoring rule, all in a compact block; the Args section is somewhat redundant with the schema but harmless. No filler sentences beyond that redundancy.

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?

An output schema exists so return formatting need not be explained, and the description gives enough on mechanics and scoring to call the tool confidently. It could be stronger by linking the computed hash to sibling tools (mt_skill_issue_vc / mt_skill_verify) that presumably consume 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?

Schema coverage is 100% and the description simply restates the schema's own wording for github_url ('GitHub repo or direct HTTPS link to SKILL.md'). No additional format details, redirect behavior, or auth requirements are added beyond what the schema already provides, so baseline 3 applies.

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?

States a specific verb and resource ('Audit an AI agent skill (SKILL.md)') and enumerates exactly what the audit covers (prompt injection, data exfiltration, tool scope violations, metadata completeness). An agent can distinguish this from sibling verification/issuance tools like mt_skill_verify or mt_skill_issue_vc purely from the description.

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?

The passing-score threshold (>= 70) implies this is a gate/validation step, but the description never states when to prefer this over mt_skill_verify or what to do with a failing result. Usage is inferable rather than explicit, and no alternatives or exclusions are named.

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