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

readOnlyHint=true already declares this a safe read, so the low bar applies. The description adds genuinely useful context beyond annotations: it discloses the return payload and imposes a real constraint ('free component's source'), telling the agent include_source may not yield source for paid components. It does not mention error/not-found behavior, but the availability caveat is meaningful added value.

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?

Front-loaded with the payoff ('Everything needed to use one item') followed by a dense enumeration of the returned fields and one short conditional sentence. No filler, though the long list is packed into a single sentence.

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 assumes full responsibility for return-value disclosure and does so thoroughly (import, props, defaults, classes, data-* values, dependencies, install command). For a 2-parameter read tool this is nearly complete; only not-found/error handling is unaddressed.

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 0%, so the description must carry the parameter burden. It explains include_source well ('read a free component's source'), including its scope limit, but says nothing about 'name' beyond implying it identifies one item. Half the parameters are effectively undocumented, matching the minimum-viable 3.

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 resource ('one item' = a component) and enumerates exactly what the response contains: import statement, every prop with fixed values and defaults, styled classes, data-* values, dependencies, install command. An agent can tell this is a single-component detail lookup rather than a search. It does not explicitly contrast itself with search_components or get_install_command, so sibling differentiation is only implicit.

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 (look up one component's full usage contract) and one condition is given: 'Set include_source to read a free component's source.' But there is no explicit when-to-use vs search_components (discovery) or get_install_command (which overlaps with the install command this tool also returns), leaving the agent to infer the routing.

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