Run Saved Search

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, so description minimally adds context. It notes the tool is 'lighter-weight than get_saved_search_results' which hints at a lighter response, but no further behavioral details (e.g., pagination handling, caching) are disclosed. Adequate but not exceptional.

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, front-loaded with core purpose. No filler, every sentence adds value. Excellent structure for quick parsing by an AI agent.

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 no output schema and good annotations, the description explains core functionality, paging, field selection, and sibling relationship. It doesn't elaborate on return format or full behavior of fields, but for a read-only fetch tool with 5 parameters, it is mostly complete. Minor gap: output_format not mentioned.

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 0%, so description must compensate. It explains search_id as 'by UUID', mentions paging via page/size, and fields projection. However, it omits output_format parameter. Partially covers the 5 parameters but not all, leaving ambiguity about output_format.

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 clearly states the verb 'Execute a saved device search by UUID and return its device results', specifying the resource (saved search) and action. It also distinguishes from sibling tool get_saved_search_results by noting it's lighter-weight when subset of fields needed.

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 explicit guidance on when to use this tool vs. the alternative get_saved_search_results ('Lighter-weight when you only need a subset of fields'). It does not explicitly state when not to use it, but the comparison implies the alternative for full results.

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