Get a component

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

readOnlyHint=true already covers the safety profile, so the description earns credit for disclosing the shape and depth of what comes back — props with defaults and requiredness, slot definitions, requirements, Livewire-inclusive snippets and working examples. It does not mention error behavior for an unknown name or the size/format of the payload, which keeps it below a 5.

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?

Two sentences, front-loaded with what is returned and closed with the action guidance. No filler or restatement of the title.

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 does the work of summarizing return contents in enough depth for the agent to know the call is worth making before authoring a view. A single required enum parameter leaves little else to explain.

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 coverage is 100% and the enum enumerates all 46 valid components, so the schema already carries the parameter meaning. The description adds nothing beyond it (no note that the name must match the enum exactly or how nested components are referenced), 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?

States a specific verb and resource ('Everything about one component') and enumerates the payload: Blade tags, props with defaults/required/behavior, slots, requirements, usage snippets and examples. That level of specificity distinguishes it cleanly from list_components, which cannot return per-prop detail.

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?

Gives an explicit trigger: 'Read it before writing the component into a view.' That tells the agent when to reach for it. It stops short of naming list_components as the discovery step or stating when-not-to-use, so it is clear context rather than full when/when-not/alternatives routing.

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