frontend_security_audit_manifest

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

Despite no annotations, the description fully discloses behavior: it states the tool is read-only, has no side effects, is idempotent, and explains the verdict logic with specific thresholds. It also lists data sources, ensuring transparency.

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 informative but somewhat verbose. However, every sentence adds value, and the structure is logical: purpose, differentiation, parameters, verdict logic, sources, and usage notes.

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?

Given the presence of an output schema, the description does not need to detail return values, but it explains the verdict types. It covers parameters, behavior, and sources thoroughly. Minor improvement could include example or note about output schema.

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 0%, but the description compensates by specifying that 'manifest' is required, 500 KB max, and 'lockfile' is optional and affects version pinning. This adds critical meaning beyond the schema structure.

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 audits a frontend package.json for security risks and returns a SHIP/CAUTION/BLOCK verdict. It explicitly distinguishes itself from security_fetch_package_vulnerabilities, which audits a single package, clarifying the scope.

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?

Provides explicit when-to-use guidance by contrasting with a sibling tool. Includes instructions for providing a lockfile and what happens without it. Also advises on feedback if the tool doesn't serve the need, covering fallback use.

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