slopsquat_scanner__scan_pip

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

With no annotations, the description carries the full burden. It usefully discloses the two finding categories (nonexistent package names, and packages first published very recently) and the underlying intent (LLM-hallucinated deps pre-registered by attackers). It does not disclose that the check requires network access to PyPI, whether it is read-only, rate-limit behavior, or how findings are shaped.

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?

One sentence, front-loaded with the action and the target files, then the two outcome classes. Slightly dense with the parenthetical explanation, but no filler sentences.

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 one-parameter, no-annotation, no-output-schema tool, the description covers what is scanned and what gets flagged, but leaves the return shape and the network/registry dependency unstated. An agent knows when to call it but not what to expect back.

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% for the single 'directory' parameter, and the description reinforces which files it looks for inside that directory, so the agent knows the expected layout. It adds a small amount of meaning beyond the schema but nothing about behavior if both files are present.

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?

States a specific verb + resource (check declared dependencies against PyPI) and names the input artifacts (requirements.txt, pyproject.toml). It also names the two distinct finding classes, so it is clearly distinguishable from slopsquat_scanner__scan_npm and dependency_auditor__audit_pip.

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?

Usage is implied by the file scope (pip projects only), but there is no explicit when-to-use guidance and no routing to siblings such as slopsquat_scanner__check_package for a single package or scan_npm for Node projects. The agent must infer the boundary from the ecosystem name.

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