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

readOnlyHint=true is consistent with a retrieval tool. Beyond the annotation, the description discloses two things annotations cannot: the return payload shape (files plus target write path) and the auth/licensing requirement (Bearer CALIPER_TOKEN on the MCP connection plus an active Pro or Team licence). It stops short of describing failure behavior when the licence 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 sentences, both front-loaded and free of filler: the return value comes first and the prerequisite second. The auth sentence packs two distinct requirements (token header and licence tier) into one clause, which is dense but still parseable.

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 only at a high level – it does not say whether the result is a list, a map of path to content, or how binary/large files are handled. Auth is covered, but error and not-found behavior is not. Adequate for a one-parameter tool, with clear gaps.

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 0% and the single parameter 'name' is undocumented in the schema. The description only implies that 'the component' is identified by this name; it adds no format, casing, or qualified-identifier guidance. That is a partial compensation for the coverage gap, not a full one.

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 specifies the resource and the payload: 'Every source file the component needs, with the path to write it to.' That tells an agent this is a full source-retrieval tool, not a metadata lookup. It does not explicitly contrast itself with siblings like get_component or get_install_command, so the differentiation is inferred rather than stated.

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?

Usage is implied by the payload description (fetch files in order to write them), and the second sentence gives a real prerequisite condition for Pro parts. However, there is no explicit guidance on when to pick this over get_component or search_components, nor what to do when only a subset of files is wanted.

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