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

No annotations are provided, so the description must disclose behavioral traits. It offers no information about return format, caching behavior, network calls, or any side effects. This is a significant gap for a tool that likely performs external queries.

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 two-word description is concise in word count but under-specified. It is not appropriately sized because it fails to convey essential functional information, making it more of a placeholder than a concise description.

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?

With no output schema, no annotations, and a merely titular description, the tool is contextually incomplete. The agent cannot determine return values, expected behavior, or appropriate usage scenarios, making the description completely inadequate.

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%: 'packages' is described as 'Package names array' and 'ignoreCache' as 'Bypass cache'. The description itself adds no parameter meaning, but the schema fully documents the parameters, so the baseline of 3 applies.

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 'Maintainers info' is a noun phrase that restates the tool name without any verb or action. It does not clarify what operation is performed (e.g., fetch, list, retrieve) and fails to distinguish the tool from sibling tools like npmMaintenance or npmScore.

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 is provided on when to use this tool versus alternatives. The description gives no context, exclusions, or mention of sibling tools, leaving the agent without criteria for tool selection.

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