query

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Execute SQL' implies the ability to run arbitrary SQL, potentially including data modification, but the description does not state whether this is read-only or allows writes, what permissions are required, how results are returned, or any pagination behavior beyond the schema. This is significant under-disclosure for a tool with no annotations.

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, focused sentence with no fluff or redundant wording. It is front-loaded with the core verb and resource. While it is concise, it could benefit from a bit more structure (e.g., separating purpose from usage guidance), but as-is it is an efficient use of words.

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?

Given the tool has 5 parameters, no annotations, and no output schema, the description is too minimal to provide complete context. It does not describe return values, side effects, result limits, or how to use the database_name parameter. For a raw SQL execution tool, critical safety and usage details are missing.

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 description mentions 'pagination and parameterization' which gives semantic meaning to the offset, pageSize, and parameters fields, but it does not explain each parameter beyond that. With 0% schema description coverage, the description must compensate more thoroughly; database_name is not mentioned at all. It adds some value but is not sufficient for a 5-parameter tool.

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: 'Execute SQL with pagination and parameterization'. This uses a specific verb ('Execute') and resource ('SQL'), and the mention of pagination/parameterization hints at capabilities that distinguish it from sibling tools like describe_table or explain_query. However, it does not explicitly differentiate from other query-like tools or name alternatives.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any exclusions, prerequisites, or preferred scenarios, such as 'for read-only queries use X instead'. Given the large set of sibling tools, the absence of any usage context is a clear gap.

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