export_bugbounty_report

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

With no annotations, the description carries the full burden. It does disclose meaningful output behavior (SHA-256 verification, OWASP/VRT dual rating, remediation guidance), but it never says whether a file is written to disk or content is returned, whether an existing finding is required, or what happens if finding_id is null.

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 bullet structure front-loads the purpose and each bullet is substantive. Yet the '(Phase 3 Engine)' label and the mojibake-encoded Vietnamese add noise, and the bullets describe report content rather than invocation guidance, so size is spent on the wrong dimension.

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?

An output schema exists, so return values need not be re-explained. But for a three-parameter tool with zero annotation coverage and zero schema descriptions, the description leaves the invocation model (which parameter triggers which report, side effects) undeclared, which is a material gap.

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 0% across all three parameters, and the description never mentions finding_id, program_id, or target_url. Nothing explains what these optional parameters select or how the enum value 'default-program' behaves, so the gap is entirely uncompensated.

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 states a specific verb and resource: it exports a Markdown-format vulnerability report, and explains the report's content (three-layer evidence, dual rating, remediation). It does not differentiate itself from siblings such as inspect_finding_or_evidence or get_pentest_dashboard, so an agent must infer which tool to pick.

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?

Usage context is implied by 'Phase 3 Engine' and by the destinations listed (HackerOne, Bugcrowd, enterprise handoff). However, no explicit when-not-to-use rule or comparison to sibling tools is provided, leaving selection to inference.

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