payload_list

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

No annotations are provided, so the description carries the full burden. It only says 'List generated payloads,' implying a read-only operation, but it does not explicitly state safety, what the response contains, whether it affects state, or any caveats. For a list tool, some behavioral detail is expected.

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 that directly states the action and resource. Every word earns its place; there is no redundancy 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?

For a simple zero-parameter list tool, the description is minimally viable, but it leaves gaps: it doesn't clarify what constitutes a 'generated payload,' whether the list is session-scoped, or what the return format looks like. Since there are no annotations or output schema, the description is the sole source of context and could be more complete.

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?

The input schema has zero properties (100% schema description coverage). Since there are no parameters, the description does not need to add parameter semantics. Baseline is 4 for zero-parameter tools.

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 'List generated payloads.' uses a specific verb ('List') and resource ('generated payloads'), clearly distinguishing it from sibling tools like payload_generate, payload_templates, and payload_host_start. However, it lacks explicit scoping (e.g., all payloads vs. current session) and does not mention alternatives, so it doesn't fully reach the highest bar.

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 provides no guidance on when to use this tool versus alternatives such as payload_templates or payload_generate. There is no mention of prerequisites, context, or exclusions. The usage is only implied by the verb 'List'.

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