All installed dependency versions

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

With no annotations, the description carries the full burden. It discloses the data source (lockfile), filtering behavior, and that it includes transitive deps by default. It is clearly a read-only list operation, though it does not mention return format or limit semantics.

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 concise sentences: the first states the action and scope, the second gives use cases. No redundant wording, and the key information is front-loaded.

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 4-parameter tool with no output schema, the description covers purpose, source, filtering, and transitive deps. Minor gaps remain around explicit return format and limit behavior, but the tool's simple list nature makes these less critical.

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 baseline is 3. The description adds semantic context for filter ('substring') and directOnly ('whole tree including transitive deps'), but does not elaborate beyond the schema for limit or projectDir, which are already well-documented.

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 clearly states 'List every dependency's installed version in this project (from the lockfile)', giving a specific verb, resource, and scope. It distinguishes itself from sibling tools by emphasizing the whole tree including transitive deps and substring filtering.

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?

Provides explicit use cases: 'Use to audit what's actually present, or to answer what version of X is in here'. This gives clear context, though it does not explicitly name when-not to use or mention alternative sibling tools.

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