Workflow: Analyze Findings

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 useful context by clarifying the tool returns instructions rather than performing the analysis, and explains why it exists as a prompt workaround. It doesn't describe the shape of the returned instructions, but that's a minor gap given 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?

Two sentences, front-loaded with the core behavior, with the client-compatibility guidance following. Every sentence earns its place.

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 single-parameter, read-only workflow tool with full schema coverage and no output schema, the description tells the agent exactly what it will get back (instructions) and why it exists. Nothing needed to call it correctly is missing.

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 coverage is 100% and the single pentest_id parameter is fully documented in the schema. The description adds a semantic constraint beyond the schema by tying the input to a 'completed' pentest, implying the ID must reference a finished engagement.

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?

States a specific verb and resource: returns step-by-step instructions for producing a prioritized remediation plan from a pentest's findings. An agent can distinguish this from data-retrieval siblings like turbopentest_get_findings, which return raw findings rather than workflow instructions.

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?

Names a clear triggering condition: use it in MCP clients such as Codex that don't support the 'analyze_findings' prompt directly. The alternative (the native prompt) is identified, though it doesn't state when to prefer raw get_findings data instead.

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