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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-obvious behavior: payment per approved answer capped by the Ask's wanted answer count, series collapsing into one row, and the rule that place-less Asks remain in `near` results. It doesn't discuss pagination or result ordering outside the series case.

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 leads with what the tool returns and then the filtering model; sentences are dense but mostly load-bearing. The payment/answer-count sentence is domain context rather than invocation guidance, slightly diluting the front-loaded structure, though it does help interpret results given no output schema.

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 8 parameters, a nested `near` object, and no output schema, the description supplies enough domain model (what an Ask is, what a series is, how pay works) plus the near-radius default to call the tool correctly. It stops short of explaining ordering or limits beyond the series case.

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 88%, so the baseline is 3; the description earns above that by explaining filter-model semantics the schema only gestures at, such as a series being one row whose members are retrieved via `series`, and that filtering follows the board's search conventions. The `does` precedence rule is already in the schema, so the description doesn't add there.

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 states a specific verb and resource ('Open asks on Asks') plus the scope of what is returned (pays, whether a model can do it), which lets an agent distinguish it from read_ask or post_ask. It never names a sibling explicitly, so differentiation is inferred from the verb rather than declared.

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 says filters work 'the same way the board's search does' and lists the filter axes (place, does, pay, words), which implies when to reach for it. However, there is no explicit when-to-use/when-not guidance and no alternative named, even though read_ask and where_to_act are adjacent choices.

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