aura_get_component

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses what the response contains (source, preview, URL), implying a read-only fetch, but says nothing about auth requirements, rate limits, or error behavior when an id/slug is absent.

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 tight sentences with the payload front-loaded and the input format tacked on second. No filler, though the fragment style for the identifier hint is slightly clipped.

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 correctly takes on the job of describing the return payload and does so at a high level. However, it leaves the two input parameters under-specified (mutual exclusivity, numeric-only id) and omits any failure mode for invalid identifiers.

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 0% and the 'id' property has no type declared, so the schema gives almost nothing. The phrase 'Numeric id or slug' partially compensates by telling the agent id is numeric and slug is a string alias, but it never states these are mutually exclusive alternatives or whether one is preferred.

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 (fetch full component detail) and enumerates the payload: HTML/Tailwind source, preview image, page URL. It differentiates itself from siblings like aura_search_components by promising 'full' detail, though it never names the alternative explicitly.

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 clause 'Numeric id or slug' hints that this is a lookup-by-identifier tool, but there is no statement of when to reach for it versus aura_search_components (discovery) or aura_install_component (install). No prerequisites or exclusions are given.

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