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

No annotations exist, so the description must carry the behavioral load. It usefully signals that the tool returns instructions rather than mutating the project ('Follow them in the user's project') and previews the return content (markup, options, pitfalls). It says nothing about read-only guarantees, permission/auth needs, or failure behavior for an unknown component name.

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: a scope/content statement followed by a direct action instruction, front-loaded with the deliverable. 'To the user's project' and 'in the user's project' repeat slightly, costing a little tightness.

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 two-parameter tool with a fully described schema the description covers the essentials, and there is no output schema to explain. However, with no annotations it should say more about whether the tool touches the filesystem and what the response looks like structurally (a single step list? per-stack sections?).

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%, so the name and settings parameters are already fully documented, including the settings key/value format and palette roles. The description adds one useful implicit point — that no stack parameter is required because the steps cover every stack — but nothing about settings beyond the schema. 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 concrete deliverable: installation steps for a Foundry44 component including markup, options and pitfalls. That distinguishes it from a naive reading of 'get_component' as a source fetcher. It never names search_components, so sibling differentiation is left to the schema text.

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?

'For any stack (plain HTML, React with or without shadcn, other)' plus 'Follow them in the user's project' implies the context of use: applying a component to the user's own codebase. There is no explicit when-not, no mention of the search_components prerequisite, and no statement about what to do if the name is unknown.

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