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

readOnlyHint=true already tells the agent this is a safe read. The description adds domain context (bundles are curated sets that install together) but says nothing about pagination, result volume, or what fields a listed bundle carries. Useful but thin beyond the annotation.

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?

One sentence, front-loaded with the verb and resource, with the clarifying example placed immediately after the term it defines. Nothing is wasted or buried.

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 list tool, the definition covers what the resource is and how it relates to installation, which is the main ambiguity an agent faces here. The only gap is that with no output schema, nothing indicates what a listed bundle entry contains (name, id, included skills).

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. No misleading hints about filtering are given, which is consistent with the empty schema.

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 ('List') and resource ('skill bundles'), then defines what a bundle is with a concrete example ('a morning routine'). This implicitly separates it from list_skills, but it never names the sibling alternative explicitly, so differentiation relies on the reader knowing what a 'skill' vs 'bundle' is.

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 phrase 'install together with one prompt' hints that this is a discovery step preceding install_bundle, but there is no explicit when-to-use, when-not-to-use, or named alternative. Usage is only implied from the resource description.

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