List Ionic Framework components

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

Beyond the readOnlyHint annotation, the description reveals the exact return fields (tag, description, url) and the semantic of url as the doc page, and clarifies that limit 100 retrieves every component.

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 tight, direct, and logically organized into a purpose, a use case, return format, and explicit exclusions—no fluff or redundancy.

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 sufficiently explains what will be returned and how it links to the documentation, making it fully actionable in 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?

Though schema descriptions already cover all parameters, the description adds actionable guidance like 'Use limit 100 to list every component' and the instruction to match the version to the user's package.json, enriching parameter understanding.

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?

Clearly states it lists Ionic Framework UI components with optional keyword filtering, and explicitly distinguishes from sibling tools by directing API reads to get_doc_page and Capacitor plugins to another server.

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?

Provides explicit when-to-use guidance ('find the component that fits a piece of UI... learn the custom element name') and when-not-to-use guidance ('Do not use this to read a component's API... Do not use it for Capacitor plugins').

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