mydatabase_execute_safe_query

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

The description discloses behavioral traits beyond annotations: it states 'Large results are automatically truncated.' This is not captured by readOnlyHint or destructiveHint. It also confirms the tool is safe and read-only, consistent with 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 two sentences, front-loaded with the main purpose, followed by a critical warning. Every sentence adds value, and there is no extraneous information. It is concise and well-structured.

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?

For a simple tool with one parameter and no output schema, the description adequately covers purpose, usage guidelines, and behavioral traits. It could optionally mention what the return value looks like, but this is not necessary for effective invocation. The presence of sibling tools covering schema exploration fills the gap.

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 coverage is 100%, and the schema already describes 'sql' as a 'SQL SELECT statement.' The description adds no further parameter-level specifics (e.g., format, escaping), so it meets the baseline expectation but does not exceed it.

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 it executes safe SELECT queries. It distinguishes itself from sibling tools by explicitly warning against using it for schema exploration, which is the role of 'search_schema'. The verb 'executes' and the resource 'safe SELECT query' are specific and unambiguous.

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 provides explicit usage guidelines: 'NEVER use this tool to understand the database structure' and 'you MUST ALWAYS use the 'search_schema' tool first before writing JOIN queries.' This gives clear when-to-use and when-not-to-use advice, along with a specific alternative tool.

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