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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description is free to add value beyond that. It does so by disclosing the access model: free items are retrievable, while Pro items require a Pro API key — genuine auth context not present in the annotations.

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?

A single front-loaded sentence leads with the payoff ('Everything needed to use one item') and then enumerates the payload. Dense but efficient, with no filler sentences.

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?

With no output schema, the description carries the burden of describing the return payload and does so thoroughly, and it adds the Pro API key access condition. Combined with fully documented parameters and safety annotations, an agent has enough to call it correctly, though routing guidance is absent.

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%, so all three parameters (slug, includeSource, includeExamples) are already documented with examples and defaults. The description adds no additional parameter-level meaning beyond what the schema provides, so the baseline 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?

States a specific verb+resource (get a component) and enumerates the returned payload (description, props, parts, dependencies, install command, source files), so an agent knows exactly what this tool fetches. It does not, however, explicitly name siblings like search_components or get_install_instructions to sharpen the boundary.

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 focuses on what is returned rather than when to call it. There is no explicit when-to-use, when-not-to-use, or routing to the obvious alternative search_components; the only usage hint is indirect (item access requires a Pro API key for Pro items).

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