find_matching

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

With no annotations, the description provides useful behavior: sorting by $ descending and excluding assigned/active-PR bounties. It could mention more (e.g., result limit, read-only nature), but the given info is sufficient for basic understanding.

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 effective sentences front-load the purpose and then add behavioral details. Every word adds value; no fluff.

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?

The description covers the core purpose and key behaviors, but lacks details on output format, result limits, and the meaning of parameters like fresh_only. Given no output schema and 4 parameters, it is slightly incomplete.

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 50%, and the description adds no extra meaning beyond the schema. It indirectly mentions skills and min_dollars but does not explain them further, nor does it address fresh_only or max_attempts.

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 clearly states the action (find), resource (bounties), criteria (skill set and dollar floor), sorting (desc by $), and exclusions. It distinguishes itself from siblings like list_bounties and get_bounty as a filtered search tool.

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 purpose is clear enough to infer when to use it: when filtering bounties by skills and minimum dollars. However, it does not explicitly state when not to use it or mention alternatives, leaving some guidance to context.

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