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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds the subscription gate and spells out the returned payload (install order, exact target paths, expo install line, provider/runtime requirements), going meaningfully beyond the annotations.

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, with the eligibility condition front-loaded before the functional description, and no filler. The second sentence is a dense run-on list, but every item earns its place by telling the agent what the call returns.

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 carries the burden of explaining the return value, and it does so concretely (file list with target paths, install line, providers, runtime rules). Combined with the subscription caveat, an agent has what it needs to call and interpret the tool.

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 slug parameter is already documented with examples ("button", "bottom-sheet"). The description adds no additional slug semantics such as valid identifier forms or lookup behavior, 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 states a specific verb and resource ("Adds one component to an existing project") and then enumerates exactly what the call yields (files in install order with target paths, the expo install line, providers, runtime rules), which separates it from siblings like get_component or find_component. It is clear but does not name an alternative to disambiguate from add_screen/update_components.

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 opening clause gives a real precondition ("Needs a subscription, except for the free foundation components"), which is useful gating context. However, there is no explicit when-to-use vs. when-not guidance and no reference to sibling tools such as find_component for discovery or update_components for edits, leaving routing to inference.

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