Get BI.ZONE program details

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

No annotations exist, so the description must carry the burden, and it does disclose the returned content in concrete terms (payout ranges, statistics, 90-day numbers, average answer time, rules markdown, scope summary) plus the flexible identifier forms. It omits what happens when a name fragment is ambiguous or matches multiple programs, and gives no indication of cost/rate limits.

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?

Two sentences, front-loaded with the tool's identity and contents, then identifier flexibility. No filler or 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?

With no output schema, the description usefully enumerates what is returned, and the schema covers all parameters. The remaining gap is edge-case behavior (ambiguous fragment, not-found handling) for a read tool that has no annotations to fall back on.

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 coverage is 100%, so all four parameters are already documented in the schema. The description's 'accepts a slug, part of the name, or a ... URL' largely restates the schema's program parameter, adding no syntax or matching-behavior detail beyond it.

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+resource ('Full profile of one bug bounty program') and enumerates what the profile contains, so an agent can distinguish it from program_stats and get_program_scope without opening any schema.

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?

Usage is implied by 'one program' and the field list, but there is no explicit guidance on when to prefer list_programs, program_stats, or get_program_scope, and no exclusions. The only routing hint (use get_program_scope) lives in the schema, not the description.

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