roboshadow_get_scan_summary

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

No annotations are provided, so the description carries the full disclosure burden. It communicates the output content ('scan details, IP vulnerability totals, and web vulnerability findings') and 'Get' implies a read operation, but it does not describe error behavior, freshness, or other side-effect information.

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 one sentence that front-loads the verb and resource, then uses a concise colon-separated list of output categories. There is no filler, repetition of the tool name, or unnecessary detail.

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?

This is a simple two-required-param read operation with no output schema, and the description plus schema provide enough information to identify and invoke the tool. It names the major return sections, although it does not enumerate individual fields or provide alternative usage guidance.

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 100%: both scanId and organisationId are already described in the input schema. The description adds no parameter-specific meaning, so it earns the baseline score of 3.

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 uses a specific verb ('Get') and precise resource ('detailed summary of one external vulnerability scan'). It further lists the three output categories, which distinguishes it from siblings like roboshadow_get_scan_ips_overview.

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 implies usage: if you need a detailed summary of a specific external scan, call this tool. However, it does not explicitly state when to use this tool over alternatives like roboshadow_get_scan_ips_overview, so the agent must infer the routing.

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