Run saved search

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

No annotations provided, so the description must disclose behavioral traits. It claims safety and cheapness but does not elaborate on permissions, error handling, pagination, or return format beyond 'rows via SearchDisplay.run'. Insufficient detail for a mutation-like execution tool.

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 sentences: purpose, pairing suggestion, and value proposition. No fluff, information is front-loaded, and each sentence earns its place.

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?

Despite moderate complexity (5 params, nested objects) and no output schema, the description omits return format, pagination behavior, and error scenarios. It does not fully equip an agent to invoke the tool correctly.

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 60%, and the description adds no extra meaning to parameters. The schema already describes 'search' as name/id, 'display' as optional, etc. With moderate coverage, a score of 3 is appropriate as the description does not compensate for missing details.

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 'Execute a SavedSearch and return its rows via SearchDisplay.run', clearly specifying the verb and resource. It distinguishes from siblings by pairing with civicrm_list_saved_searches, and values it as the safest/cheapest way to run complex queries.

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 provides clear context for when to use: for admin-curated complex queries. It suggests pairing with civicrm_list_saved_searches to discover searches. However, it does not explicitly list exclusions or alternative tools for ad-hoc queries.

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