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

With no annotations, the description carries the full burden of disclosing behavior, but it only states a vague domain. It does not indicate whether the operation is read-only, what data it returns, whether it makes network requests, or any other behavioral traits. This is a significant gap for a tool that likely queries npm data.

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 under-specified—a single phrase that does not earn its place by providing critical information. While it is short, it is not effectively concise; it omits essential details and lacks any front-loaded actionable content.

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 tool with 2 parameters, no output schema, and no annotations, this description is severely inadequate. It does not explain what maintenance metrics are, how they are calculated, what result format to expect, or how this tool differs from the many related npm sibling tools. The agent cannot reliably invoke or interpret the tool's output.

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 input schema provides descriptions for both parameters ('Package names array' and 'Bypass cache'), covering 100% of parameters. However, the tool description adds no extra meaning about how these parameters relate to analysis or what 'maintenance metrics' means. The schema descriptions are minimal, but enough for the baseline of 3.

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 'Maintenance metrics analysis' is a noun phrase rather than a clear verb+resource statement. It does not specify what the tool does (e.g., 'fetch', 'calculate', 'report') and is barely more informative than the tool name itself. It does not distinguish from sibling tools like npmQuality or npmRepoStats.

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?

The description provides no guidance on when to use this tool versus alternatives such as npmScore, npmDeps, or npmQuality. There is no mention of intended scenarios, prerequisites, or exclusions. The lack of any usage context leaves the agent without direction.

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