list_programs

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

With no annotations, the description carries the behavioral transparency burden. It discloses meaningful pagination behavior (all_pages vs. page), the default of all_pages, and the private_only filtering behavior. It does not mention authentication requirements or rate limits, but as a straightforward read operation with an output schema, the disclosed behavior is reasonably complete.

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 compact and front-loaded with the tool's core purpose, followed by a clean, minimal Args section. Every sentence adds value; there is no filler or redundant schema repetition.

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 list tool with no required parameters, no nested objects, and an existing output schema, the description covers everything an agent needs to invoke it correctly. It specifies fetch-all behavior, page selection, and private-only filtering in a self-contained way.

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 0%, so the description is the only source of parameter meaning. It compensates well by explaining all three parameters beyond their types and defaults, especially the conditional relationship between all_pages and page. It stops short of detailing page size or response pagination metadata, but the core semantics are clear.

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?

States a specific verb ('List') and a specific resource ('bug bounty programs you have access to'), including the key differentiator of private invite-only programs. This clearly distinguishes it from siblings like get_program, which retrieves a single program, and list_reports, which lists reports.

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 explains argument-level behavior but provides no guidance on when to choose list_programs over get_program or list_reports, and mentions no alternatives or exclusions. An agent is left to infer the appropriate use case from the name and sibling list.

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