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

Annotations only rule out read-only and destructive labeling, so the description carries the burden of explaining side effects. It discloses that the report is private to the submitter and program owner and promises a tracking id and estimated payout, which is useful behavioral context beyond the structured fields.

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 short sentences, each with a distinct job: state the action, add the scope constraint, and describe privacy/output. There is no filler or repetition of schema details.

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 write action with no output schema, the description covers the important call context: scope, privacy, and the returned identifiers. It could be more complete by noting that the program owner assigns final severity or by routing to sibling tools, but those are refinements rather than blockers.

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%, so the schema already defines every parameter including the severity enum and the optional target. The description adds no new parameter-level meaning beyond mentioning the chosen severity, which is already in the schema, so a baseline 3 is appropriate.

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 opens with a concrete verb and object ('Submit a vulnerability report to a live program'), making the core action unmistakable. It adds the private-to-owner detail and mentions return values, though it doesn't explicitly contrast itself with sibling tools like disclose_finding or publish_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 establishes the context of live-program submission and warns to stay in scope, which implies this is the initial reporting action. It does not name alternative tools (disclose_finding, publish_finding, review_finding) or state when not to use them, so the agent must infer the distinction from names alone.

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