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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description builds on that with behavior those hints cannot convey: the response names extra dependencies with install commands, and without a premium key only free components resolve while other names return a key-acquisition notice. That gating and partial-success behavior is exactly what an agent needs to interpret a non-source response.

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?

Three sentences, front-loaded with what is returned, then dependencies, then routing and gating. The dependency sentence is dense and stacks react, framer-motion, lucide-react, gsap and three in one clause, but each clause carries information an agent would otherwise have to discover by trial.

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 single-parameter read tool with no output schema, the description covers return payload, non-source extras, dependency install needs, the alternative tool, and the unauthenticated fallback. Nothing an agent needs in order to call this correctly or interpret its result is missing.

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 parameter's schema already explains the source of the name, case-insensitive matching, and an example. The description's 'once you know the exact name' reinforces exactness but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 opens with a specific verb and resource: 'Returns the complete, copy-ready React/TSX source of one component as designed.' It also states the payload goes beyond source (notes on images and extra files), which lets an agent distinguish this from sibling get_component_styled without opening either schema.

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 gives an explicit trigger ('Use it once you know the exact name') and names the alternative with the condition that selects it: 'use get_component_styled instead when the component should take on an extracted brand style.' It also states the freemium boundary and that list_components/search_components mark which names are free, so the agent knows what to try when a call fails.

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