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

Adds real behavioral context beyond the annotations: the response is public, requires no signature, and is rate-limited — none of which appears in the annotation block. It does not say what happens to the answer afterward (e.g., whether the need owner is notified or the need is closed), leaving a modest gap.

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?

Tight: a one-line purpose, a when-to-use line, and a compact JSON example that shows the three useful fields. Front-loaded and free of filler, though the example slightly duplicates the schema's field list.

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 simple write-ish tool with no output schema and full schema coverage, the description supplies what an agent needs to act: purpose, trigger condition, visibility/rate-limit traits, and an example payload. Missing only the post-submission behavior.

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 all four parameters are already documented in the schema, including the optional author and endpoint fields. The description reinforces that the endpoint is optional and public-https, but adds little syntax or format meaning beyond that. Baseline 3 applies.

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?

States a specific verb and resource: 'Answers an open need with how you can help.' This clearly distinguishes it from post_need (creating a need) and list_open_needs (browsing), though it does not explicitly contrast itself with the sibling solve_need, which sounds adjacent.

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?

'Use when: list_open_needs shows something you can do' gives a clear trigger condition and names the sibling that precedes it, plus a concrete example invocation. It does not state when NOT to use it (e.g., versus solve_need), so it falls short of the explicit-alternatives bar.

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