Poc Record

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

The annotation readOnlyHint: true declares a read-only operation, yet the description describes recording a PoC and confirming a finding — both state-changing operations. 'Confirm the finding' implies transitioning a finding's status, and 'this is how a finding becomes confirmed' reinforces state modification. This is a serious inconsistency that misleads the agent about side effects, mirroring the create_record contradiction pattern.

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 well-structured with the core purpose front-loaded in the first sentence. Three short paragraphs cover purpose, usage context, and parameter requirements without excessive verbosity. Minor redundancy exists between paragraphs 1 and 2, both restating the human-reproduction concept, but the overall structure is clean and purposeful.

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?

The description provides strong contextual framing for the security workflow — explaining why human verification matters and when this tool fits in the assessment lifecycle. However, it leaves operational gaps: the source of finding_id, what 'confirm the finding' changes in practice, and how this integrates with the broader findings workflow are unspecified. For a 6-parameter tool with 4 required fields, the operational mechanics are incomplete.

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 schema has 0% description coverage. The description partially compensates by naming reproduction, expected_result, and observed_result and explaining their significance via the 'hypothesis vs. PoC' distinction. However, finding_id, evidence_excerpt, and impact_limit_note are entirely unexplained — the agent receives no guidance on where finding_id originates or what the optional fields should contain.

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 clearly states the tool's purpose: recording a human-reproduced proof-of-concept and confirming a finding. It distinguishes this from automated validation by naming the vulnerability classes (IDOR, auth bypass, RCE, blind SSRF) where tool-only proof is insufficient. However, the read/write contradiction with the readOnlyHint annotation slightly muddies the operational purpose.

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 explicitly identifies when this tool should be used: for vulnerability classes where no tool should confirm findings on its own, requiring human reproduction and written documentation. It also implies when not to use it — when automated validation suffices or when observed_result is absent (making it a hypothesis rather than a PoC). It does not explicitly name alternative sibling tools, but the scope boundary is clearly drawn.

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