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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond the annotations: it discloses the return content (contact ids matched 'currently'), which matters because no output schema exists. It stops short of noting pagination or result-size limits.

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 sentences with the core behavior front-loaded and no wasted preamble. The trailing REST endpoint reference is arguably redundant metadata, but it is compact and potentially useful for API-oriented callers.

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 correctly compensates by stating what is returned (matching contact ids). For a two-parameter read tool with readOnlyHint annotations, the essential information is present; only edge-case behavior like result limits or archived-contact interaction is left unstated.

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 both saved_search_id and exclude_archived are already documented in the schema. The description adds no syntax, format, or constraint detail beyond what the schema supplies, so the 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?

The description states a specific verb ('Run') and resource ('one saved search') and clarifies the output ('return the ids of the contacts it currently matches'). This clearly separates it from the sibling wildapricot_list_saved_searches, which enumerates searches rather than executing them.

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?

Usage is implied by the phrasing 'Run one saved search,' but there is no explicit guidance on when to prefer this over alternatives or on the prerequisite of obtaining a saved_search_id from list_saved_searches. 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.