List Searches for Device

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which cover the safety and behavioral profile. The description adds context about filtering by device UUID and search type, but does not disclose any additional behavioral traits beyond what annotations imply. Since annotations carry the burden, a 3 is appropriate.

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?

The description is two concise sentences. The first states the core function, the second provides the triage context and optional filter. No extraneous words; every sentence adds value. This is an exemplary model of conciseness.

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 the output schema exists (filling in return value details), the description fully covers what the tool does, how to use it (required UUID, optional filter), and its purpose. The complexity is low, and the description is complete for an AI agent to invoke it 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?

The input schema has 0% description coverage, so the description must compensate. It clarifies device_uuid as 'by UUID' and search_type as a filter by saved-search type, but does not explain output_format or what format strings are acceptable. This provides partial but insufficient coverage for all three parameters.

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 it lists saved device searches that match a given device by UUID, with optional type filtering. The phrase 'Triage primitive' and the question 'which saved searches does this device match?' provide a specific, actionable purpose that distinguishes it from sibling tools like list_saved_searches (which lists all searches) or get_saved_search_results (which returns results for a specific search).

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 explicitly frames the tool as a triage primitive and gives the exact question it answers ('which saved searches does this device match?'), indicating when to use it. It mentions optional filtering by search type. However, it does not explicitly state when not to use it or compare it with alternatives like advanced_device_search, but the context is clear enough for an AI agent.

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