npmLicenseCompatibility

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

The description adds minimal behavioral context beyond the annotations. Annotations already indicate read-only, open-world, and idempotent behavior. The description does not mention that the tool may make network requests, use caching (despite the ignoreCache parameter), or what happens during failure. It also does not explain the output format.

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?

The description is a single sentence, very concise. However, it could be slightly more informative without being verbose. It front-loads the core purpose but omits valuable context about behavior and output.

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 the complexity of license compatibility checking and the lack of an output schema, the description is insufficient. It does not explain what constitutes compatibility, how results are returned (list or boolean), or whether the tool uses external data sources. An agent would have limited understanding of what to expect.

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 descriptions for both parameters. The tool description adds no additional meaning beyond what the schema provides. A baseline of 3 is appropriate because the schema already describes the parameters adequately, but the description could have clarified what 'compatibility' means in this context.

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 the action ('Check') and the resource ('license compatibility between multiple packages'). It distinguishes the tool from sibling tools like npmAlternatives, npmCompare, and npmVulnerabilities, which cover different aspects of npm packages. However, it could be more specific about what 'compatibility' entails.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, such as requiring the packages to exist on npm, or situations where this tool is not appropriate. The description implies usage for license checking but offers no exclusions or context.

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