search_volunteer_times

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds no behavioral context beyond that, such as whether results are paginated, what format the query should take, or that the search might return incomplete results.

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?

At five words, the description is extremely short but lacks necessary details. Conciseness should not come at the expense of needed information; a search tool with a single parameter and multiple siblings requires more context.

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?

Given the tool has one parameter, a simple schema, and many sibling tools, the description is incomplete. It does not explain what 'volunteer times' are, what the query searches against, or how results are structured, leaving significant gaps for correct invocation.

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% with a description for the 'query' parameter. The tool description does not add meaning beyond what the schema provides, so baseline 3 is appropriate.

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 'Search for volunteer times' identifies the verb 'search' and resource 'volunteer times', providing a clear but generic purpose. It fails to distinguish from sibling tools like list_volunteer_times (which likely lists all) and get_volunteer_time (which retrieves a single one), leaving ambiguity about what 'search' entails versus listing.

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?

No guidance is given on when to use this tool versus alternatives. With siblings like list_volunteer_times and get_volunteer_time, the description does not explain the context for searching (e.g., when a query is needed) or when to prefer this over listing.

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