hackerone_program_audit_log

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

With no annotations provided, the description must carry the full behavioral burden, but it only reveals that the tool is a program-owner API. It does not state whether the operation is read-only, what response format to expect, how pagination works, or what errors may occur.

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 very short and contains no filler words, but it is under-specified to the point of being more a label than a helpful definition. The parenthetical structure provides minimal extra value beyond repeating the tool name.

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?

Given the lack of annotations and no output schema, the description is insufficient on its own. It omits return values, pagination behavior, and auth prerequisites beyond the vague 'program-owner API' tag, so an agent would struggle to invoke the tool correctly without additional context.

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 input schema fully describes both parameters, including the default page_size and constraints, so the description does not need to add much parameter detail. Still, the description adds no semantic meaning beyond what the schema already provides, keeping this at the baseline 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 identifies the resource as a program audit log and notes it is a program-owner API, but it lacks an explicit action verb such as 'get' or 'list'. It mostly restates the tool name, so while the general purpose is inferable, it is not clearly articulated.

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?

There is no guidance on when to use this tool versus any of the many sibling tools. The parenthetical 'program-owner API' hints at an access restriction but does not explain when this tool should be selected over alternatives.

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