websex_scan_summary

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

With no annotations, the description carries the full burden. It says only that it summarizes 'without discarding their output' but doesn't explain permissions, limits, return shape, or side effects. It provides essentially no behavioral information beyond the name.

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 short sentence, but it is under-specified rather than concise. Front-loading is absent because there is no real content to front-load.

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 tool with an output schema but no annotations and a completely undescribed parameter, the description is inadequate. It does not explain what gets summarized, how results are aggregated, or what the summary will contain, leaving critical gaps.

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 0% and the single parameter 'results' is an array of unrestricted objects. The description does not clarify the expected structure, required fields, or size limits of the results argument, leaving the agent with no useful semantic guidance.

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 name websex_scan_summary and the description 'Summarize complete WebSex tool results' only loosely restate the tool's resource. It doesn't state what kind of results (e.g., HTTP responses, scan artifacts) or what a summary contains, and it does not distinguish the tool from other WebSex summary utilities.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as directly inspecting results. An agent cannot tell when this summarization is appropriate versus using raw tool output.

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