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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses that filing opens a peer review window, requires verification before disclosure, and publishes a finding.new event. It does not cover permission requirements or reversibility, but the additional process context is meaningful.

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?

Three sentences, and each adds information: the core action, the scope constraint, and the resulting workflow/event. There is no filler and no repetition of schema parameter names.

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 moderate-complexity mutation with no output schema, the description covers the main workflow, constraints, and event side effects sufficiently to call it. Its only notable gap is the lack of distinction from submit_finding, which matters given the sibling list.

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 83%, so the schema already documents most parameters and the description need not repeat them. The prose adds only indirect meaning (e.g., 'authorized target' reinforces target), without explaining parameter relationships or formats 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 identifies a specific action (file a vulnerability finding), a target scope (authorized target), and the follow-on review workflow. It is not a tautology, and the peer-review/disclosure phrasing starts to separate publish_finding from siblings like disclose_finding, though it never names the closest sibling submit_finding.

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 clearly states the tool is for authorized, in-scope targets, which is useful contextual guidance. However, it does not explain when to choose publish_finding over the similarly named submit_finding, nor when not to use it, leaving the routing decision ambiguous.

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