query

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

No annotations are provided, so the description carries the full burden. It discloses the read-only nature and allowed statements, but does not cover error behavior, authentication needs, or what happens if non-allowed queries are attempted. It provides adequate but not exhaustive transparency.

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 concise sentences that front-load the purpose and immediately provide constraints. No extraneous information, every word adds 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?

For a tool with one parameter and an output schema, the description is fairly complete: it defines allowed queries and read-only semantics. It could mention that results are returned in the output schema, but that is likely documented elsewhere. Overall sufficient for correct usage.

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 has one required string parameter without any description. The tool description adds meaning by specifying the query must be a read-only SQL statement (SELECT, etc.), but lacks examples or syntax requirements. This partially compensates for the 0% schema coverage.

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 read-only query on an SQLite database, listing specific allowed SQL commands (SELECT, SHOW, DESCRIBE, EXPLAIN, WITH). This verb+resource structure effectively distinguishes it from sibling tools like 'execute' (for writes) and 'describe'.

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 specifies that only certain commands are allowed and that the database is read-only, providing clear context for when to use this tool. However, it does not explicitly mention alternatives like 'execute' for writes, though the sibling list implies such tools exist.

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