ydb_query

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

With no annotations, the description carries full burden but fails to disclose safety traits (e.g., read-only vs mutation), idempotency, or side effects. It only says 'run a SQL query', which is insufficient for an agent to gauge risk.

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 sentence, which is concise, but it is too terse given the lack of annotations and low schema coverage. Some additional context would be justified.

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 an output schema exists (which helps with return values), the description omits important behavioral context such as safety, limits, or error conditions. For a tool that executes arbitrary SQL, more completeness is needed.

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 0%, so the description must compensate, but it only mentions 'SQL query' without elaborating on the 'sql' parameter's format, length constraints, or typical usage. The schema provides only type 'string'.

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 action ('run a SQL query') and the resource ('YDB database'), but it does not differentiate from the sibling tool 'ydb_query_with_params', which presumably has similar functionality. The agent may be confused about when to use this one vs the other.

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?

No guidance is provided on when to use this tool versus alternatives like 'ydb_query_with_params' or 'ydb_explain_query'. There is no mention of prerequisites, return handling, or selection criteria.

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