scan_and_report

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

No annotations provided. The description adds only the save location of reports. It omits behavioral details like resource intensity, persistence of data, or any side effects, which are important for a combined scan and report tool.

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?

Two sentences, front-loaded with purpose. The first sentence states the action, the second adds benefit and save location. No unnecessary words.

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?

The description covers the combination aspect and save location, but lacks details on what constitutes a 'full security scan,' how output is structured, or how to interpret results. Given the complexity of 7 parameters and many siblings, more completeness would be beneficial.

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%, so baseline is 3. The description does not add further parameter meaning beyond what the schema already provides.

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 it runs a full security scan and generates reports in one step, distinguishing it from separate scan and report tools. However, 'full security scan' is somewhat vague and could be more specific about its 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?

The description implies use when avoiding data transfer between tools, but does not explicitly state when not to use or mention alternatives. It provides general guidance but lacks explicit exclusions.

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