List Dev Kit Component Variants

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

The readOnlyHint annotation already declares a safe read operation. The description adds behavioral context by specifying that the tool 'returns names only,' which clarifies the return shape and avoids expecting full component data. It doesn't mention edge cases like empty results or ordering, but for a simple list tool this is sufficient.

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 two sentences, with the key action stated immediately. It wastes no words and every sentence earns its place by explaining purpose and the alternative tool.

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?

This is a simple read-only list tool with one parameter, an output schema, and a clear description of return semantics ('names only'). The description, combined with annotations and schema, fully covers what the agent needs to know. The existence of an output schema also means return values need not be elaborated further.

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 input schema provides 100% coverage for the single 'component' parameter, including an example. The tool description adds no additional parameter detail beyond the schema. As schema coverage is high, the baseline of 3 is appropriate.

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 all available variant names for a Dev Kit Italia web component, with a specific verb (lists) and resource (variant names). It also notes the output is names only, which distinguishes it from sibling tools like devkit_get_component_markup that fetch full markup.

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 guidance to use devkit_get_component_markup for fetching a specific variant, establishing an explicit alternative. It implies this tool is for discovering variant names. However, it doesn't explicitly state 'when not to use' beyond the markup reference, so it falls just short of a 5.

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