DepShield MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully lists the evaluation criteria (downloads, maintenance, license, deprecation) and output format (0-100 score), compensating for the missing output schema. However, it omits safety indicators (read-only vs destructive), error handling (e.g., non-existent packages), or rate limiting concerns.

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 consists of two efficient sentences with zero waste. It front-loads the action ('Assess') and uses a colon-delimited list to specify evaluation factors, ending with the output specification ('Scored 0-100'). Every word earns its place.

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 single-parameter tool without output schema or annotations, the description is reasonably complete. It discloses the scoring range and evaluation dimensions, providing sufficient context for invocation. It could be improved by mentioning error cases (e.g., package not found) or confirming the read-only nature of the operation.

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 has 100% description coverage for the single 'name' parameter ('npm package name'). The description adds no additional parameter context, examples, or format constraints beyond what the schema already provides, meeting the baseline expectation for high schema coverage.

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 tool assesses package health and trustworthiness using specific metrics (downloads, maintenance, license, deprecation) and produces a numeric score (0-100). However, it does not explicitly differentiate from sibling tool 'check_dependency' which may have overlapping functionality.

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 like 'check_dependency', 'deep_scan', or 'audit_project'. There are no stated prerequisites, exclusions, or conditions for use.

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