hackerone_list_program_members

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

With no annotations, the description carries the full behavioral burden. It does disclose an authorization trait (program-owner API) and the resource being returned, but it does not mention pagination, response shape, or side effects. For a list operation these are partially implicit, so partial credit is warranted.

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 free of filler, but it is a sentence fragment that lacks a verb, and the useful qualifier is tucked into a parenthesis. It is concise but structurally under-built.

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 two-parameter list tool, the schema covers invocation arguments and the description conveys the resource and auth class. However, with no output schema and no annotations, an agent still lacks detail about the member object shape and pagination semantics, so completeness is only partial.

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 already documents both parameters at 100% coverage: program handle or numeric id, and page_size with a default of 25. The description adds no parameter-level meaning, so it earns the baseline without extra credit.

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 ('program team members') and an API context ('program-owner API'), but it is a noun phrase with no explicit verb such as 'list' or 'return.' The action must be inferred from the tool name, so it is clearer than a tautology but not a specific verb+resource statement.

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 instead of siblings like get_program_details, list_programs, or get_program_scope. The parenthetical 'program-owner API' hints at an access context, but it never states conditions, exclusions, or alternatives.

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