List searches

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that sessions are 'retained,' but does not explain what a search session contains, whether results are included, how results are paginated, or any filtering behavior.

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 a single clean sentence with no wasted words and the core action is front-loaded. It is appropriately sized for a listing tool, though its brevity contributes to the gaps in other dimensions.

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 two undocumented parameters, no output schema, and no explanation of what a 'retained progressive search session' actually is, the description leaves significant gaps for an agent trying to call this tool correctly. It does not cover filtering or return content.

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% and the two parameters (deviceId, deviceName) are undocumented in the schema. The description does not mention either parameter or clarify whether they are filters or required, so it provides no semantic meaning at all.

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 verb (list) and resource (retained progressive search sessions), but 'progressive search sessions' is undefined jargon and there is no explicit differentiation from siblings like start_search, get_more_search_results, or stop_search. An agent can infer it retrieves past searches, but the exact scope is vague.

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?

There is no guidance on when to use this tool versus alternatives such as start_search or get_more_search_results, and no exclusions or prerequisites are mentioned. The only implied usage comes from the word 'retained,' which is not enough to route an agent reliably.

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