hackerone_get_report_activities

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

With no annotations provided, the description carries the burden of behavioral disclosure. It indicates the tool returns a timeline of activities and enumerates categories, but it does not describe ordering, pagination behavior, response structure, or auth requirements. It is adequate for a straightforward read operation, but not richly transparent.

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, focused sentence that front-loads the core concept and uses a concise colon-delimited list to convey scope. Every word adds value and there is no redundant or filler content.

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 tool with only two parameters, both fully described in the schema, the description covers the essential return-value concept and activity categories. There is no output schema, but the tool is simple enough that the timeline description plus schema documentation provides sufficient context for correct invocation.

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 both report_id and page_size are already documented in the input schema. The description does not add parameter-level meaning beyond the schema, which aligns with the baseline score for high schema coverage.

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 clearly identifies the tool's purpose: retrieving an activity timeline for a HackerOne report, and it lists the specific kinds of activities included. This differentiates it from siblings like hackerone_get_report and hackerone_get_report_with_conversation by emphasizing the full activity stream rather than just report details or conversation messages.

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 gives clear context for when to use the tool: when a report's activity history is needed, including comments, state changes, bounty awards, and triage responses. It does not explicitly name alternatives or exclusion cases, but the scope is evident enough for an agent to select it appropriately.

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