default_query_database

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

No annotations are provided, so the description must carry full burden. It only mentions 'query' which implies a read operation, but does not disclose any behavioral traits such as whether it is read-only, destructive, required permissions, or error handling. This is insufficient for safe invocation.

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 a single concise sentence with the action front-loaded. While concise, it sacrifices completeness; however, for a simple query tool, it is appropriately sized.

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?

Despite having an output schema, the description lacks details on how to use parameters like filtering, sorting, and pagination. The 5-parameter tool with 0% schema descriptions needs more context to be fully usable.

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 has 0% description coverage, so the description must compensate. It only clarifies the required parameter (data_source_id) but provides no meaning for filter_json, sorts_json, start_cursor, or page_size, leaving the agent to infer from schema names alone.

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 queries database contents, specifying the resource (database) and verb (query). It also distinguishes from siblings by noting to use data_source_id, not database_id, which differentiates it from tools like default_retrieve_database.

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 provides clear context by instructing to use data_source_id instead of database_id, implying the correct parameter. However, it does not explicitly state when to use this tool over alternatives like default_query_data_source or provide exclusions.

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