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

The description specifies the primary behavior—returning full source code—but with no annotations it does not disclose error behavior for unknown names or explicitly guarantee read-only semantics. The 'get' verb implies a read operation, but this is not made explicit.

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 a single, clear sentence with no redundant wording. It directly conveys what the tool does and how the input is used.

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 simple single-parameter retrieval tool, the description provides sufficient context about the expected input and output. It does not describe failure cases or output formatting, but these are less critical given the simple schema and the availability of sibling listing/search tools.

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?

The tool description adds no parameter-specific detail, but the input schema fully describes the name parameter with an example. Since schema coverage is high, the baseline score 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 states that the tool returns the complete, copy-ready React/TSX source code for a component given its name. This clearly identifies the verb, resource, and input, and distinguishes it from listing, searching, and styled-component siblings.

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 implies use when the agent already knows the component name and needs its source code. It does not explicitly contrast this with get_component_styled or explain when to prefer search_components first.

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