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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: this is a prerequisite process document that prescribes a workflow (research, targeted interview, approval gate) rather than a data lookup. It does not describe output format, but with no output schema that is a small gap.

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?

A single sentence with the imperative 'DO THIS FIRST' front-loaded, then a compact list of what the skill covers. Every clause carries distinct information and nothing is wasted.

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?

For a zero-parameter, read-only knowledge-retrieval tool with no output schema, the description gives enough: what phase it governs, when to invoke it, and the workflow it prescribes. The only missing element is an explicit statement that the response is guidance text the agent should follow.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is empty and fully covered, so no compensating detail is required.

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?

The description identifies a specific resource — the discovery skill covering business research, gap-only user interviews, and build-plan approval — which clearly separates it from siblings like get_skill_page_structure or get_skill_publish. It never explicitly says it returns instructional guidance, but the 'how to...' framing makes the retrieval nature apparent. Clear verb-implied resource, minor ambiguity about return shape.

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?

'DO THIS FIRST for any new landing page' gives an explicit triggering condition and ordering relative to other skills. It does not name a specific alternative or state when-not-to-use, but the sequencing rule is strong enough that an agent knows to call this before other skill tools.

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