List SQLite query sessions

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 that only currently retained streaming sessions are returned, which is useful context, but says nothing about return format, pagination, or how sessions become retained.

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?

A single front-loaded sentence with no filler, which fits a simple list operation. It is efficient, though its brevity contributes to the missing usage and parameter context.

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?

For a tool with two undocumented optional filter parameters, no output schema, and closely related siblings (db_query_start/next/close, list_sessions), the definition leaves key gaps: what 'retained' means, whether filters are required together, and when this tool belongs in a query workflow.

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 description is completely silent on deviceId and deviceName, so the agent gets no hint that these are optional filters or how they interact. This fails to compensate for the missing schema documentation.

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 (SQLite streaming query sessions), and 'currently retained' narrows scope. It is clearer than the generic sibling list_sessions, but does not explicitly distinguish itself from db_query_start/db_query_next/db_query_close or explain what a retained session is.

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?

No when-to-use guidance, no alternatives, and no condition telling the agent to prefer this over list_sessions or the other db_query_* tools. 'Currently retained' implies a context but does not instruct.

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