rolldev_db_query

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states 'Run a SQL query' without addressing permissions, side effects (e.g., destructive writes), rate limits, or what happens on execution (e.g., returns result set or error). This is a critical gap for a database mutation 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?

The description is a single sentence, front-loaded with the action. However, it is underspecified; while concise, it fails to earn its place by providing minimal useful context. A more informative sentence could maintain conciseness while adding value.

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 the tool executes arbitrary SQL, it lacks essential context: expected output (e.g., result rows), execution behavior (e.g., read-only vs. write), and potential risks. No output schema exists, and the description does not compensate, leaving an LLM uncertain about what to expect.

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% with parameter descriptions, so the baseline is 3. The description adds no extra meaning beyond the schema, merely saying 'Run a SQL query' without detailing parameter roles. It neither improves nor degrades the schema's clarity.

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 verb 'Run' and resource 'a SQL query in the RollDev database', which distinguishes it from sibling tools like composer or CLI operations. However, 'RollDev database' is vague without specifying which database, though the schema later reveals a default database.

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 no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use it, or comparison to sibling tools like rolldev_magento_cli which might also execute SQL.

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