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

readOnlyHint=true already declares the safety profile, so the bar is lower. The description adds genuinely useful context beyond the annotation: it returns only contact ids, and it is a live evaluation ('currently matches'), which the annotation and schema do not convey. It does not discuss result size limits or whether the saved search filters archived contacts on its own.

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?

Two tightly written sentences: the operational behavior is front-loaded and the raw API route follows as supporting detail. No filler.

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 no output schema, the description does the work of stating that the return value is a list of contact ids, which is the key missing piece. It falls short only on scale concerns (pagination or result caps) that an agent running a broad saved search would want to know.

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 both saved_search_id and exclude_archived documented inline, so the baseline is 3. The description adds no format or constraint detail beyond the schema.

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 (run), the resource (one saved search), and the exact payload returned (ids of currently matching contacts). This cleanly separates it from the sibling wildapricot_list_saved_searches, which enumerates searches rather than executing one.

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 name and description imply usage well enough, but there is no explicit when-to-use or when-not-to guidance, and no mention of the natural alternative (list_saved_searches to obtain the saved_search_id first). The agent must infer the workflow.

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