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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds useful context that the entries are admin-defined and lists the returned fields, plus the underlying GET endpoint. It does not mention pagination behavior or result limits, which keeps this at a solid-but-not-rich 3.

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 compact sentences, with the purpose and return fields front-loaded before the endpoint mapping. Every clause carries information and nothing is redundant.

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 and no parameters, the description compensates by naming the return fields (id, name, description) and the scope of the search set. A mention of pagination or ordering would make it fully self-contained, but nothing essential to calling the tool is missing.

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?

The tool takes zero parameters, so the baseline is 4. There are no parameter semantics to clarify, and the description correctly describes a no-argument enumeration of account-level saved searches.

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 ('List') and resource ('contact saved searches defined by admins'), and the parenthetical enumerates the returned fields (id, name, description), so the agent knows exactly what comes back. It is naturally distinguished from the singular wildapricot_get_saved_search sibling by its plural list scope.

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 tool name and the 'admin-defined' qualifier, which tells the agent these searches were configured by administrators rather than ad-hoc. However, there is no explicit when-to-use statement and no alternative sibling is named (e.g., routing to wildapricot_get_saved_search for a single definition).

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