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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to indicate whether this is a read-only check, what inputs it expects (beyond schema), what output format it returns, or any side effects. The single phrase provides no transparency.

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?

While very short, this is under-specification rather than conciseness. The three-word description does not earn its place by conveying any useful information; it simply restates the tool's purpose in noun form.

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?

The tool has 3 parameters, a required array, and no output schema, yet the description provides no context about the expected behavior, parameter roles, or return value. It is completely inadequate for an agent to select and invoke this tool correctly.

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 100% with brief but present descriptions for packages, ignoreCache, and projectLicense. The tool description itself adds no meaning beyond the schema, but per the baseline for high coverage, a 3 is appropriate.

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 'License compatibility check' is essentially a tautology of the tool name 'npmLicenseCompatibility'. It does not state a specific verb and resource, nor does it distinguish this tool from its many npm-related siblings like npmAlternatives or npmCompare.

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?

There is no guidance on when to use this tool versus alternatives. It does not say anything about checking licensing before using certain packages, comparing project vs dependency licenses, or any other usage context.

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