get_dbinfo

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Retrieve' implies a read operation, but it does not specify whether special permissions are needed, how verbose affects output, or what the return format is. No behavioral traits beyond the basic operation are disclosed.

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?

One concise sentence, front-loaded with the primary action and resource. Every word earns its place with no filler.

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 simple with three optional parameters and no output schema. The description provides enough context to understand its core purpose, but could be more complete by explaining what diagnostics are included or that a device connection is required. It is minimally sufficient.

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 each parameter (serial, verbose, packageName) described in the schema. The description adds no meaning beyond the schema, only restating the optional package filter. Baseline 3 is appropriate.

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 uses a specific verb ('Retrieve') and resource ('SQLite database statistics and diagnostics'), and clarifies it uses dumpsys dbinfo. It distinguishes from siblings like query_sqlite (queries data) and get_dumpsys (general dumpsys) by focusing on database diagnostics.

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 implies usage through its focus on SQLite stats, but does not explicitly state when to use it versus alternatives like query_sqlite or get_dumpsys. No exclusions or alternative guidance are provided.

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