aflpp.whatsup

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

With no annotations provided, the description carries the full burden. It only says 'Run' without disclosing any behavioral traits such as whether the tool reads/writes files, requires existing workspaces, or produces output. There is no mention of side effects, permissions, or expected behavior.

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 short sentence and is concise and front-loaded. However, it is so terse that it borders on under-specification, but that is more a completeness issue than a conciseness one.

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 6 parameters, no output schema, and no annotations, this one-sentence description is completely inadequate. It does not explain return values, parameter semantics, or any necessary prerequisites or context.

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%, so the description must compensate but does not. It only hints at an output directory, while there are 6 parameters (including workspace, timeout_ms, summary_only, etc.). No parameter is explained or given additional meaning beyond the 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 states a specific verb ('Run') and resource ('afl-whatsup on an AFL++ output directory'), but it does not explain what afl-whatsup actually does or how it differs from sibling tools like aflpp.status or aflpp.campaign_summary. The name and description are clear only if the agent already knows afl-whatsup.

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 guidance on when to use this tool versus alternatives. No mention of scenarios, exclusions, or relationships to sibling tools. The description is a bare instruction with no usage context.

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