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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real behavior: demo competitions (demo: true) are silently excluded unless include_demo is true, and results are paged with next_cursor. It also enumerates the returned fields (reward, deadline, status, summary, entries). It stops short of stating default page size or ordering, but the behavioral picture is solid.

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?

It is front-loaded with the use case and the key naming clarification, and every sentence carries information. The middle sentences are dense with stacked parentheticals ("id, handle, status", "demo: true, which take no entries"), which costs a little readability but no real waste.

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 a full output schema, complete parameter documentation, and rich annotations, the description only needs to cover selection, filtering surprises, and pagination — and it does all three. An agent has everything required to call this correctly on the first attempt.

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 baseline is 3; the description adds meaning on top by framing status values as "the ones still running", clarifying include_demo's effect, and instructing to pass next_cursor back as cursor. It does not add anything for category or limit beyond the schema, keeping it just above baseline.

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 opens with a specific verb and resource — finding open coding bounties and the USDC reward each pays — and explicitly maps the naming confusion ("make.fun lists each bounty as a competition"). It also names the sibling it feeds into (get_competition), so an agent can distinguish it from other list_* tools at a glance.

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?

It gives an explicit entry condition ("Use this when you want to find open coding bounties"), tells the agent to "pass status open for the ones still running", and routes onward with "Start here, then get_competition for one." That is when-to-use plus a named alternative, leaving nothing to inference.

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