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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description redundantly says 'Read-only, free' – consistent. It adds value beyond annotations by explaining that skills are the orchestration layer and that the tool lists both bundled and in-app skills. This context helps the agent understand the nature of the returned list, though it doesn't describe output format or pagination. No contradiction with 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?

The description is a single, reasonably concise sentence that leads with the core action ('List the bundled Hermoso SKILLS') and then elaborates. It uses em-dashes effectively to add context without excessive verbosity, though it could be broken into shorter sentences for easier scanning.

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?

Given there are no parameters and no output schema, the description sufficiently explains the tool's function and its relationship to get_skill. It mentions the types of skills (bundled, in-app, creative recipes) and gives examples, which is enough for an agent to decide if this is the tool to use. It doesn't describe the return format, but for a list tool that's less critical.

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 description has nothing to add about parameter meaning. The schema is empty and covers 100% of params. Baseline for 0 params is 4; the description appropriately focuses on what the tool lists rather than parameters.

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 the tool lists 'bundled Hermoso SKILLS' and elaborates what these are (multi-step workflow instructions) with concrete examples (research an ad space, plan+render a finished ad). It also mentions the additional in-app strategy skills and creative recipes, making the resource unambiguous. It distinguishes itself from the get_skill sibling by explicitly pointing to it for loading a bundle.

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 clear context for when to use this tool: to see the available skills, and it instructs to call get_skill to load a bundle afterward. However, it does not explicitly state when not to use this tool or compare it with other listing tools (e.g., list_playbooks, list_library). It implies usage well but lacks explicit exclusions.

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