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

Beyond the read-only and closed-world annotations, it discloses that required packages accompany the tests and that an item without tests produces shipped: false. It leaves the precise returned structure and the fact that tests are supplied for later checking rather than executed by this tool largely implicit.

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?

Three compact sentences front-load the returned resource, then give the use case and the important empty-result behavior. There is no filler, although the opening noun phrase is slightly less direct than an explicit retrieval statement.

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 simple three-parameter read tool, the description covers the resource, intended use, notable contents, and no-tests behavior, which is especially useful without an output schema. The remaining gaps are parameter-specific guidance and a clearer statement of output form and non-execution behavior.

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?

With only 33% schema description coverage, the description needs to compensate for the undocumented type and packageManager parameters, but it never explains their roles. Their enums and default are visible in the schema, yet the description adds no guidance about when type is needed or how packageManager affects the returned package information.

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 identifies the resource as an item's shipped Vitest and Testing Library tests, including their subject matter and required packages. It is distinguishable from siblings such as get_item and get_examples in practice, but it does not explicitly contrast them or directly state that the tool retrieves, rather than runs, the tests.

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?

It gives a concrete when-to-use condition: checking that an item still works after the agent or user changes it. It does not provide exclusions or name an alternative for obtaining source code, examples, or general item details.

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