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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. With no output schema, the description usefully carries the return-shape burden by naming the install list contents (versions, peer deps, install commands, license notes), which is real added value beyond the structured fields.

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?

A single dense sentence with the action front-loaded and the payoff (exact install list plus its contents) immediately following. No filler, no repetition 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?

Given no output schema, the description compensates by describing the returned install list, and it signals the two input modes. It omits edge behavior such as what happens if both packages and workflow are supplied, but for a read-only resolution tool the definition is largely sufficient.

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% with clear per-parameter descriptions and an enum for platform, so the schema does the heavy lifting. The description only hints that packages and workflow are mutually exclusive alternatives and adds no format or limit detail beyond the schema.

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 (resolve) and resource (Offline Protocol packages/workflow) and even enumerates the output artifacts: versions, required/peer deps, install commands, license notes. This clearly separates it from list_packages or get_package, though it never names a sibling to sharpen the contrast.

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 phrase 'packages, or a workflow' implies the two are alternative inputs, which is mild usage guidance, but there is no statement of when to reach for this versus search_packages/get_package, nor any prerequisite such as needing a platform first.

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