hackerone_get_report_with_conversation

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the core return content—the full conversation and resolution—and 'Shows' implies a read operation, but it does not describe response structure, pagination, depth of report details, or any access constraints. This is adequate but leaves material behavior implicit.

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 two short sentences with no filler. The core resource is front-loaded, and the second sentence adds useful context about what the conversation contains. Both sentences earn their 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?

The tool is simple (one fully documented parameter) and the description conveys the key differentiator, the conversation. However, with no output schema and no explicit boundary against sibling tools like hackerone_get_report_activities, the description is not fully complete for an agent that must decide between several similar report-related tools.

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% for the single parameter report_id ('The HackerOne report ID'), so the schema fully documents the parameter. The description adds no additional meaning about the parameter, matching the baseline of 3.

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 resource—a report with its full triage conversation—and clarifies what it shows (questions asked, path to resolution). It is distinguishable from siblings like hackerone_get_report_activities even though it lacks an explicit verb; the tool name supplies the get action.

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 implies that this tool is for retrieving the triage conversation and its resolution, but it does not explicitly state when to choose it over hackerone_get_report or hackerone_get_report_activities. No exclusions or alternative routing are provided, leaving the choice mostly to name inference.

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