hackerone_analyze_report_patterns

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

There are no annotations, so the description carries the behavioral disclosure burden. 'Analyze' implies a read-only operation, and 'your recent reports' scopes the data, but the description does not explicitly state that nothing is modified, how 'recent' is defined, or whether authentication or specific report ownership is required. It provides some behavioral context but leaves important details 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 a single, front-loaded sentence that immediately communicates the tool's purpose and lists the key output categories with no filler. Every word contributes meaningful information.

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 simple tool with one optional parameter, the description communicates the main purpose and output dimensions effectively. It does not describe the exact response shape or define 'recent', but the absent output schema is partially compensated by the precise list of analytics provided. Slightly more detail on the scope of 'recent reports' would make it fully complete.

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 only parameter, page_size, is fully described in the schema with its range and default behavior. The description does not add any meaning beyond what the schema already provides. Given 100% schema description coverage, a baseline of 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 states a clear action ('Analyze') applied to a specific resource ('your recent reports') and lists concrete output dimensions: severity/state distribution, top programs, and weakness types. It is easily distinguished from sibling reporting tools like hackerone_search_reports, though it does not explicitly name or contrast sibling tools.

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 the tool is for high-level aggregation and pattern analysis rather than retrieving individual reports, but it provides no explicit when-to-use guidance, exclusions, or mention of alternative tools. The intended use case is reasonably inferable but not directly stated.

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