saved_queries

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

The description lists four actions with brief behaviors (store, execute, return, remove), but no annotations exist to cover safety or side effects. It lacks details on persistence, authentication, error handling, or what happens when a query is run (e.g., result format). Basic actions are described but not deeply.

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 very concise, with two sentences covering the overall purpose and detailed actions. It avoids unnecessary words. However, the inclusion of '[BUILD tier]' adds minor context but slightly disrupts flow. A more structured format (e.g., bullet points) could improve readability.

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 zero parameters and no output schema, the description must compensate, but it fails to specify how to indicate the desired action (missing parameter). It also doesn't describe the return format for 'list' or 'run' actions. The tool is incomplete for reliable invocation by an AI agent.

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 is empty, yet the description implies there should be an 'action' parameter to specify what operation to perform. This creates a contradiction: the agent cannot know how to pass the action. The description adds meaning beyond the schema but does so inconsistently, leading to confusion.

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 tool's purpose: managing a personal library of reusable SELECT queries. It lists four specific actions (save, run, list, delete), making it easy to understand. It differentiates from sibling tools like 'query_sql' by focusing on personal, reusable queries.

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 is provided on when to use this tool versus alternatives such as 'query_sql' or 'analyze_table'. The description does not mention prerequisites, context, or situations where this tool is preferred. The '[BUILD tier]' hint is vague and insufficient.

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