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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely mentions two topics without explaining what the tool actually does, what data it queries, or what the output looks like. There is no mention of side effects, rate limits, or any operational behavior.

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 extremely brief, which is concise, but it is under-specified to the point of being unhelpful. It is a single phrase that adds minimal value beyond the name. While it is not verbose, it does not earn its place by providing necessary information.

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 simple schema and existence of an output schema, the description still fails to provide essential context such as what the tool returns, how the input is used, or what 'supply chain risk' entails operationally. The description is far from complete for an agent to call the 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?

The schema has one parameter 'q' with no description (0% coverage). The description does not explain what 'q' should represent, such as a package name, dependency string, or other input. Without any parameter explanation, the agent cannot infer how to use it.

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 states 'Supply Chain Risk: Dependency vulns + typosquatting' which indicates the tool covers dependency vulnerabilities and typosquatting, but it lacks a clear verb or resource. It doesn't explicitly say what the tool does with the input, making it more of a label than a functional description. It is slightly more specific than a pure tautology, hence a 2.

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. The sibling list includes 'typosquat' which likely overlaps, but the description doesn't mention it or any other alternatives. No context or exclusions are provided.

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