Workflow: Compare Pentests

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds important context by clarifying that this tool returns instructions rather than performing the comparison itself, which is behavior beyond the annotations.

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 two sentences, front-loads the tool's output behavior, and then gives the client compatibility condition. Every sentence contributes useful information without repetition.

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 two-parameter, read-only workflow helper with full schema coverage and no output schema, the description is mostly complete. It explains what is returned and when to use the tool, though it could say more about the shape of the returned instructions.

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%, with both baseline_id and current_id documented as earlier and later pentest UUIDs. The description adds only that the pentests should be on the same target and implies baseline/current ordering; it does not add syntax or format details 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 uses a specific verb and resource: it returns step-by-step instructions for diffing two pentests on the same target. It also clarifies that the output shows what's new, fixed, and persistent, distinguishing this workflow helper from direct pentest retrieval tools.

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?

It explicitly says to use this in MCP clients like Codex that don't support the 'compare_pentests' MCP prompt directly. That gives a clear condition, though it does not name any sibling tool alternatives or exclusion cases beyond the unsupported prompt.

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