execute_query

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

No annotations are provided, so the description must carry the full behavioral burden. It mentions that write operations are possible, implying mutation, but omits critical details such as whether changes are persisted, reversible, or if any confirmation is required. This is a significant transparency gap for a potentially destructive raw SQL tool.

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?

Two short, direct sentences with no filler. The primary verb and resource are front-loaded, and each sentence earns its place by stating the core action and the type of operations allowed.

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 complex tool that executes arbitrary SQL with no output schema and no annotations, the description is incomplete. It does not explain return value format, error handling, side effects, or how to use the optional params parameter. The tool's power and risk demand richer guidance.

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 coverage is 100%, so the schema already documents all parameters adequately. The description adds minimal extra meaning beyond 'raw SQL' and 'cached database', which somewhat enriches the context but does not materially enhance parameter understanding beyond the 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?

The description clearly states the tool executes a raw SQL query on a cached database and explicitly enumerates supported operations (SELECT/INSERT/UPDATE/DELETE). This distinguishes it from sibling tools like list_packages and get_schema, which are introspection-only.

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 provides some implied usage context (e.g., 'raw SQL query on a cached database') but does not explicitly state when to prefer this tool over siblings, or mention prerequisites like checking schema or listing tables first. No exclusions or alternative tool references are given.

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