assess_risk

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is '@slow' and spans multiple domains, but does not explicitly state that it is read-only, which data sources it queries, or any side effects. The output schema covers return structure, but the behavior beyond speed is somewhat opaque.

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 concise and front-loaded with the core purpose and a performance warning ('@slow'). The 'USE WHEN' list is directly relevant and adds no fluff. Every sentence and clause 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?

Given the tool's complexity (26 parameters) and the absence of annotations, the description is relatively sparse. It provides high-level usage scenarios but does not explain parameter interactions (e.g., asset_id skipping broad queries), how results are aggregated across domains, or how to interpret the output. The rich schema and output schema help compensate, but the description alone leaves gaps for such a feature-rich tool.

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%, so parameter descriptions exist. The tool description adds value by mapping natural language to specific parameters, e.g., 'cloud risk in AWS' implies provider='aws' and scope='cloud', and 'container vulnerabilities' implies scope='containers'. This semantic mapping goes beyond the schema's literal field descriptions.

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 states a clear, specific purpose: cross-domain risk assessment across VMs, cloud, containers, web apps, certificates, and assets. The 'USE WHEN' examples further specify intent ('what's our risk?', 'show me cloud risk in AWS'). This distinguishes it from siblings like security_overview by emphasizing the cross-domain aggregation.

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 a 'USE WHEN' section with concrete example queries, giving clear context for when to invoke the tool. It does not explicitly mention alternative tools or when not to use it, so it falls short of a 5, but the examples are strong enough to effectively guide selection.

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