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

Annotations already declare read-only, idempotent, closed-world behavior. The description adds meaningful context beyond that: it describes exactly what is returned and warns that enum values must be qualified with their component (e.g. 'DrylButton.ButtonVariant.Secondary') because bare enum names do not compile. It does not cover failure behavior such as unknown component names.

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?

Two sentences, front-loaded with the core purpose and followed by a critical usage caveat. Every clause contributes information and there is no repetition of schema or annotation content.

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 one-parameter read-only tool with an output schema and rich annotations, the description is complete: it states what the tool returns, why the output is structured that way, and the key enum-qualification rule an agent needs to apply the results 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?

Schema description coverage is 100%, and the single 'name' parameter is fully documented in the schema, including case-insensitivity and the optional 'Dryl' prefix. The description adds no parameter-specific semantics beyond implying a single component name.

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 states a specific verb and resource: retrieving 'the exact public API of one DRYL component', and enumerates what that includes (parameters, enum members, methods, Razor example). It is clear without naming siblings, though it does not explicitly contrast with search_components or get_tokens.

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?

Usage is implied by 'one DRYL component' and the detailed output contents, but there is no explicit statement of when to choose this over search_components or get_tokens. The enum-qualification warning is useful but concerns how to consume the result, not when to invoke the tool.

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