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

No annotations are provided, so the description carries full burden. Only mentions 'risk:low' and 'read-only', but fails to disclose what happens on query failure, authentication needs, or connection behavior. Minimal behavioral information.

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?

Single-sentence description is very concise. However, it could be slightly more structured (e.g., separated risk and type). No wasted words, but front-loading of key info could be improved.

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?

With 2 parameters, full schema coverage, no output schema, and no annotations, the description is minimally adequate. It doesn't explain return format, error handling, or execution context (e.g., connection pooling). Gaps exist.

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% with brief parameter descriptions. The description adds no additional meaning beyond the schema; it merely restates the parameter purposes. Baseline 3 applies since schema does the heavy lifting.

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 explicitly states 'Execute a read-only SQL query against a Postgres database', providing a specific verb and resource. It clearly distinguishes from sibling tools, which are mostly niche APIs for specific services.

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 for read-only queries but does not provide explicit guidance on when to use this tool versus alternatives. No exclusions or context about prerequisites are given.

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