query_database

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

With no annotations, description states read-only, local backup operation, and treats content as data (not instructions). Also mentions relation resolution. Lacks details on error handling or performance, but covers key safety and behavioral traits.

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?

Three concise sentences: purpose, prerequisite, safety. No redundant phrases. Front-loaded with the core action.

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?

Covers purpose, prerequisite, safety, and output nature. Lacks return format details (e.g., JSON structure), but given no output schema and sibling context, it's mostly complete for a query tool.

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%, so description adds context like the meaning of 'readable property values' and relation resolution, which clarifies output and ties to parameters like properties. Also explains dataSourceId origin from describe_backup.

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?

Specifically states it returns 'rows of one database/data source' with resolved relations, distinguishing from siblings like describe_backup (metadata) and get_page (single page). The verb 'query' with clear resource and scope.

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?

Explicitly says 'Use describe_backup first to get a dataSourceId', providing a prerequisite and linking to sibling. Also states it's read-only and operates on local backup files, implying when to use. Could include when not to use, but clear enough.

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