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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description does not contradict these. It adds useful behavioral context by stating the return shape (`tag`, `description`, `url`) and the default version behavior, giving an agent confidence about side effects and output expectations.

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 well-structured and front-loaded with the core purpose, followed by usage guidance, return format, and exclusions. A few phrases are slightly redundant (e.g., 'Use limit 100 to list every component' restates the schema), but overall every sentence adds useful context and nothing is unclear.

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?

Even without an output schema, the description explicitly names the returned fields, explains the default version, gives a query example, and provides alternative tool routing. This is enough for an agent to invoke the tool correctly and interpret its results without additional context.

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?

All three parameters are fully described in the schema, and the description reinforces each: `limit` is tied to listing every component, `query` is illustrated with 'modal', and `version` is linked to matching the user's package.json. The parameter meanings are clear and actionable beyond the raw 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?

The description clearly states a specific action ('List') on a specific resource ('UI components of Ionic Framework') and distinguishes this tool from siblings by explicitly routing API reads to get_doc_page and Capacitor topics elsewhere. This makes the tool's purpose immediately obvious and unambiguous.

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?

It provides explicit when-to-use guidance ('find the component that fits a piece of UI before building it by hand'), when-not-to-use guidance (API reads, Capacitor plugins), and practical tips like using limit 100 to list every component. Sibling alternatives are named directly, so an agent knows exactly when to choose this tool.

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