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

The readOnlyHint already establishes that this is a safe read operation. The description adds that results include title, agency, dates, and volunteers needed, and identifies the underlying endpoint, but it does not discuss pagination behavior or how the various filters interact beyond what the schema already states.

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?

Three short sentences with no wasted language: returned fields, filters, and endpoint are each stated once. The list behavior is front-loaded and the description is easy to scan.

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 an 8-parameter, zero-required list tool with no output schema, the description gives enough to understand what is returned and how to narrow results. The schema carries the detailed parameter documentation, so the description is mostly complete, though it could mention paging context more explicitly.

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 100%, so parameter meaning is already fully documented in the schema. The description mentions agency, title, and status filtering, but it does not add syntax or interpretation beyond the schema and omits the date filters and show_inactive parameter.

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 gives a specific verb and resource ('List volunteer needs (opportunities)') and names the returned fields (title, agency, dates, volunteers needed). It is clearly a list operation and distinct from the singular 'get_need' sibling, though it does not explicitly mention that sibling.

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 says the tool can be filtered by agency, title, or status, which implies its use for finding needs. However, it gives no explicit when-to-use guidance, no exclusions, and no comparison to alternatives such as get_need or list_need_responses.

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