check_npm_package_exposure

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

With no annotations, description discloses search scope (workflow runs, PRs, default branches) and CI-only limitation. Could mention it's read-only but overall adequate.

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?

Two sentences, front-loaded with purpose, then adds critical use guidance. No wasted words.

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?

Missing description of return value or output format. Without output schema, agent cannot infer what results look like. Other aspects covered well.

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%, baseline 3. Adds value by clarifying empty versions array behavior and showing example package name format ('@velora-dex/sdk').

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?

Clearly states it's an 'Am I Affected?' check for npm packages on CI side, distinguishing it from developer machine checks. Uses specific verb 'searches' and resource 'monitored repos'.

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?

Explicitly guides when to use: 'Org-wide (CI-side)' and provides crucial instruction to call a sibling tool for complete coverage. Includes 'IMPORTANT' note with alternative.

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