query_sqlite

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

With no annotations, the description carries full responsibility for behavioral disclosure. It mentions the debug/root prerequisite but fails to warn that the tool can execute arbitrary SQL commands, including destructive operations like DELETE or DROP, with no confirmation. This is a significant transparency gap.

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 two sentences, front-loaded with the core purpose, and wastes no words. The critical debug/root note is included without bloat.

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?

The tool is complex because it executes raw SQL, yet there is no output schema and the description doesn't explain return format, error behavior, or side effects. The debug/root limitation is present, but missing output/return details makes it incomplete.

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 schema covers all parameters with descriptions and examples, so the baseline is 3. The tool description adds no extra parameter semantics beyond what the schema already provides.

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 SQL queries/commands on a SQLite database within an app's sandboxed directory. It uses a specific verb and resource and is distinct from siblings like get_dbinfo or execute_shell_command.

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 gives clear context (executing SQL against an app's sandboxed database) and includes an important prerequisite/exclusion: only works on debuggable apps or rooted devices/emulators. It doesn't explicitly call out alternatives, but the constraint is valuable usage guidance.

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