queries_list

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

Description minimally restates the read-only nature implied by annotations (readOnlyHint: true). Does not disclose pagination, filtering behavior, or scope of 'saved queries' beyond the annotation.

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?

Single sentence is efficient and front-loaded, but may be too brief to convey important details like pagination and filtering options.

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?

With 6 parameters, pagination, and output schema, the description omits key context about filtering (q, tags) and pagination (page_size, page_token). Sibling tools like queries_get are not referenced.

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 has 50% description coverage; three parameters (tags, page_size, page_token) lack descriptions. The tool description adds no parameter information, relying solely on schema.

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?

Description clearly states 'List saved SQL queries,' specifying the action (list) and resource (saved SQL queries). It distinguishes from related tools like queries_get (single query) and query_history_list (history).

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 guidance on when to use this tool versus alternatives such as queries_get or query_history_list. Missing context for filtering or pagination usage.

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