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

Annotations already establish readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds the materially useful facts that the check is static (nothing is executed) and that it only works against public repos. It stops short of saying whether results are paginated or how findings are ordered.

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?

The core scope and the defect list are front-loaded in the first sentence, followed by two short sentences for usage and the alternative. The middle catalogue of checks is dense but each item is a distinct failure mode that 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?

With no output schema, the description carries return expectations by enumerating the finding categories, which is enough to know what comes back. It doesn't describe result shape or severity ordering, but nothing critical to calling the tool correctly is missing.

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?

One required parameter at 100% schema coverage, so the schema already defines github_url with its URL format. The description only reinforces the 'public GitHub repo' constraint, which is a modest addition over the structured field.

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?

Opens with a specific verb plus resource ('Static check of every SKILL.md ... in a public GitHub repo') and enumerates exactly which defects it detects, so the agent knows precisely what it produces. It never names the sibling preflight_skill, so the differentiation from that tool is left implicit rather than stated.

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?

Gives an explicit trigger ('Use before installing or publishing a skill pack') and routes measurement-of-live-triggering to an alternative, the skillcheck CLI. It does not address when not to use it, nor does it contrast with the sibling preflight_skill.

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