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

Annotations already declare non-readOnly, openWorld, non-idempotent and non-destructive, but the description adds real value with 'public' (responses are visible to others) and 'rate-limited', which the annotations do not convey. It stops short of saying whether you can respond more than once or whether the answer can be edited or retracted.

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?

One short lead sentence with the visibility and rate-limit caveat front-loaded, followed by a compact example. Nothing is padded, though the example is formatted inline in a way that slightly muddles scanning.

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 public, non-idempotent write tool with no output schema, the description omits what happens after answering: whether the need is notified, whether answering multiple times is allowed, or what is returned. The safety and visibility profile is covered, but the post-call behavior is not.

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 every parameter is already documented with constraints. The inline example usefully illustrates a realistic call with need_id, text and endpoint together, but adds no semantic detail beyond what the schema already states.

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: answer an open need by describing how you can help. It is clearly distinct from post_need and list_open_needs, though it does not explicitly separate itself from solve_need or offer_capability, which an agent might confuse with it.

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 description implies usage (respond to an existing open need rather than creating one), but gives no explicit when/when-not guidance and never names the alternative tools. An agent must infer the distinction from solve_need or offer_capability on its own.

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