agentest_query_db

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

No annotations provided. Description adds the debuggable build requirement and implies read-only intent ('verify DB state'), but does not clarify if arbitrary SQL (including mutations) is allowed, nor does it describe error handling or output format.

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 sentences, no fluff. The first sentence immediately conveys the tool's action and scope. Highly efficient.

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's simplicity and lack of output schema, the description covers the essential aspects: purpose, usage, and prerequisite. Minor omission: return format (rows) would be helpful but not critical.

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% and parameter descriptions in the schema are adequate. Description adds minimal extra meaning (mentions Room and testing context) but does not significantly enhance parameter understanding.

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 it runs a SQL query against an app SQLite database for verifying DB state after test actions. It distinguishes from sibling tools which cover other testing aspects like device info or logs.

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?

Provides explicit use case ('verify DB state after test actions') and a prerequisite ('Requires a debuggable build'). Does not mention alternatives or when not to use, but sibling tools are sufficiently different.

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