query

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It states the tool executes SQL queries but doesn't cover critical aspects like whether it's read-only or destructive, authentication requirements, rate limits, error handling, or result formats. This leaves significant gaps for a database interaction tool.

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 extremely concise with a single sentence that directly states the tool's function without any unnecessary words. It's front-loaded with the core purpose and appropriately sized for what it communicates, making it efficient and easy to parse.

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 complexity of executing SQL queries against a database, the description is incomplete. With no annotations, no output schema, and minimal behavioral transparency, it fails to address important aspects like result handling, error conditions, security implications, or performance considerations. The description alone is insufficient for safe and effective tool usage.

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 doesn't add meaningful parameter semantics beyond what the input schema already provides. With 100% schema description coverage, the schema fully documents the single 'query' parameter. The description's mention of 'Teradata SQL' slightly reinforces the schema's 'dialect of Teradata SQL' but doesn't provide additional syntax, format, or constraint details.

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 ('executes') and target resource ('SQL query against the Teradata database'), providing specific verb+resource pairing. However, it doesn't distinguish this tool from potential sibling tools that might also execute queries or interact with the database in similar ways, preventing a perfect score.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites, appropriate contexts, or exclusions, leaving the agent without usage direction. Sibling tools like list_tables or show_tables_details might be related, but no comparison is made.

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