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

With annotations already covering read-only/idempotent/no-destruct, the description adds substantial behavioral context: exactly what data each platform exposes (YesWeHack full severity x asset-value table, HackerOne scope but no numeric rewards, Bugcrowd neither and it reports that). This tells the agent what to expect back and prevents false assumptions per platform.

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?

Three sentences, front-loaded with the tool's identity, and the follow-on sentences about platform data availability each earn their place by setting return expectations. No filler, though the platform breakdown could be tightened.

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 read-only lookup with no output schema, explaining per-platform return contents (including platforms that return nothing) covers the main uncertainty. Minor gaps remain: exact-match vs fuzzy handle resolution and how the login-walled/absent case surfaces to the caller.

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 50%: handle is documented in the schema with concrete slug examples, while platform is an enum without a description. The description restates 'platform + handle' but adds no new format or matching semantics, so the schema still does the heavy lifting.

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 names a specific verb (retrieve one program) and resource (bug-bounty program) and pins identity to platform + handle, which implicitly separates it from bounty_programs_search / bounty_new_programs. However, it never names those siblings, so the distinction is inferable rather than explicit.

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 pick this tool over the two obvious siblings (bounty_programs_search, bounty_new_programs) or on prerequisites such as needing an exact slug rather than a name. The description is entirely about return-shape differences, not selection context.

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