aflpp.coverage_summary

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

With no annotations provided, the description must disclose behavioral traits. It mentions the underlying tool 'afl-showmap -C' but does not state safety (read-only vs side effects), performance implications, output format, or prerequisites. This is insufficient for a tool that likely executes the target on multiple inputs.

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, front-loaded sentence with no redundant words. It efficiently conveys the core action and context, scoring high on conciseness and structure.

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 8 parameters, no annotations, and no output schema, this description is too sparse. It omits return value expectations, parameter relationships, and caveats such as execution time or data volume, leaving significant gaps for an agent to safely invoke the 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 description coverage is 0%, and the description does not explain any of the 8 parameters. It does not map 'AFL++ output directory' to specific parameters like out_dir or workspace, nor does it clarify the required target_cmd or optional timeouts. The description adds no parameter meaning beyond the raw schema.

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 the specific verb 'Measure', names the resource as 'corpus coverage', and specifies the method 'using afl-showmap -C' on an 'AFL++ output directory'. This clearly distinguishes it from siblings like aflpp.whatsup (status) and aflpp.campaign_summary (campaign results).

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 for measuring coverage of a corpus but provides no explicit guidance on when to choose this tool over alternatives like aflpp.showmap or aflpp.campaign_summary. There are no exclusions or alternative recommendations.

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