security_fetch_package_risk_brief

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

No annotations are provided, so the description carries full burden. It discloses that data is refreshed on each call, lists data sources (OSV.dev, deps.dev, PyPI, npm registry), and specifies return fields. However, it does not explicitly state that the tool is read-only, though that is implied by its purpose.

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 a single paragraph with multiple informative sentences. It is front-loaded with the core verdict purpose. While it packs a lot of information, it remains relatively concise and every sentence adds value. It could benefit from breaking into bullet points for readability.

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 (not shown but noted), the description does not need to explain return values in depth. It covers purpose, usage, behavioral traits, rate limits, auth, and feedback mechanism. However, it lacks explicit parameter explanations, which are partially compensated by the 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%, so the description must add meaning. It mentions 'package' but does not elaborate on the three parameters (package_name, ecosystem, version) beyond what the schema provides. The description lists return fields but not parameter constraints or examples, which would help an agent select correct values.

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 returns a single SHIP/CAUTION/BLOCK verdict for any package, combining CVEs, license, maintainer health, and transitive count. It distinguishes itself from sibling tools like security_fetch_package_vulnerabilities and security_fetch_licence_analysis by providing a consolidated risk verdict.

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 explicitly targets 'security engineers performing pre-inclusion package review' and provides fallback guidance: if the response is not suitable, call report_feedback with specific fields. It also mentions rate limit and no auth required, giving clear when-to-use and when-not-to-use context.

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