db_select

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

No annotations are provided, so the description carries the full burden. It does not explicitly state that this is a read-only operation, nor does it mention any side effects, authentication requirements, rate limits, or return format. While 'Select' implies non-mutating, it does not disclose behavioral traits beyond what the schema already says.

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 that is front-loaded with the primary action ('Select data') and includes key qualifiers ('from a table' and 'optional filters and sorting'). Every word earns its place, and there is no padding or redundancy.

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?

While there is no output schema to clarify return values, the description is adequate for a simple select tool. It covers the core operation, and the schema handles the parameter details thoroughly. However, given the tool has 7 parameters and nested objects, a brief mention of pagination (limit/offset) or how filters are applied would increase completeness, but the current level is sufficient for most agents.

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 description coverage is 100%, as every parameter has a description. The tool description only restates 'optional filters and sorting' without adding new meaning to the parameters. It does not clarify how filters combine (AND/OR) or how order/ascending interact beyond the schema's basic descriptions, but the baseline of 3 is appropriate given high schema coverage.

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's function: 'Select data from a table with optional filters and sorting.' It uses a specific verb ('Select') and resource ('table'), and it distinguishes the tool from siblings like db_insert, db_update, and db_delete, which handle different operations.

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 clear usage: it is for retrieving data from a table with optional filtering and sorting. However, it does not explicitly exclude more complex query tools like sql_execute_raw or mention when to prefer this over db_count. The context is clear but no direct alternatives are given.

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