im_execute_select

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

No annotations provided, so the description fully carries the burden. It clearly discloses that only read operations are permitted and lists all blocked operations. This gives the agent a complete safety picture.

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?

Two concise sentences, front-loaded with the core action, and no redundant words. Every sentence adds value.

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's simple nature (2 parameters, no output schema), the description is complete: it explains what it does, constraints, and when to use it. No missing information.

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 descriptions in the schema are already clear. The tool description repeats the same information (e.g., 'Comments are not allowed', max_rows cap) without adding new parameter-level detail. Thus it does not add value beyond the schema.

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 that the tool executes ad-hoc SELECT queries and positions it as an escape hatch when dedicated BAU tools are insufficient. This distinguishes it from sibling tools like im_get_breaks or im_search_items.

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?

Explicitly states that only SELECT and WITH…SELECT queries are allowed, blocking INSERT, UPDATE, DELETE, DDL, EXEC, and comments. It also guides when to use it: as an escape hatch when BAU tools don't cover the query.

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