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

With no annotations, the description carries the full burden of behavioral disclosure. It adds useful context by describing what the list contains and by directing readers to get_skill for an installable file, implicitly indicating list_skills does not install or fetch full skill content. However, it does not explicitly state that the operation is read-only or side-effect-free, which is a notable gap for a tool with zero annotation support.

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?

Three sentences with no wasted words. The purpose is front-loaded, the sibling pointer is in the second sentence, and the practical use-case guidance closes it. Every sentence adds value.

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 list tool with no output schema, the description is complete: it specifies the scope (this workspace), the contents (standard procedures, Higgs Hub library, included with every workspace), and the next step to obtain a skill (get_skill). An agent has everything needed to use it correctly.

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?

The tool has zero parameters, so the baseline is 4. The description adds no parameter-level detail because none is needed; the empty schema already covers all input concerns.

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 clearly states a specific verb ('List') and resource ('the skills this workspace offers your agent') and explains exactly what those skills are. It also differentiates itself from the sibling get_skill by explicitly directing users there to fetch an installable SKILL.md file, so an agent can tell list_skills apart from related 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?

The description gives explicit guidance: 'Start here if someone asks what Higgs Hub can help them with, or asks to install their workspace's skills.' It also points to the alternative get_skill for fetching a single skill, making the when-to-use boundary unmistakable.

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