find_programs

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

No annotations are provided, so the description carries the full behavioral burden, but it says nothing about read-only behavior, pagination, default result limits, authentication needs, or return shape. The only behavioral hint is that filters can be combined.

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 a single short fragment, so it is technically concise, but it is under-specified rather than efficient. It front-loads the resource but omits the essential context needed to call the tool.

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 tool with 12 parameters, no annotations, no output schema, and incomplete parameter descriptions, the description is far too sparse. It does not explain what is returned, how filters combine, or how results are ordered or limited.

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 only 42% across 12 parameters, and several parameters such as tags, platforms, min_bounty, wildcard_only, and free_submission_only have no descriptions. The description contributes no parameter semantics beyond the vague phrase 'combined filters'.

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 (programs) and implies filtering, but 'discovery' is a vague verb and 'combined filters' adds little specificity. It does not distinguish this tool from siblings such as get_program, program_brief, search_targets, or find_program_by_target.

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 alternatives, no exclusions, and no prerequisites. With many sibling tools that retrieve or search programs, an agent has to infer the intended use case entirely.

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