execute_parameterized_query

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions execution with saved definitions and defaults, omitting details about return format, error handling, caching behavior (maxAge), or side effects. This is insufficient for a tool with 4 parameters.

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, well-structured sentence without unnecessary words. However, it could include more context without verbosity, so it earns a 4 rather than 5.

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?

With 4 parameters, no output schema, and no annotations, the description lacks essential context such as return format, error behavior, and how the parameters object interacts with saved definitions. This is insufficient for an execution tool.

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%, so the baseline is 3. The description adds no additional meaning beyond the schema descriptions (e.g., that maxAge controls caching, parameters override defaults, or useSavedDefaults applies omitted values).

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 identifies the tool's action ('Execute'), the resource ('saved parameterized query'), and the specific behavior ('using its saved parameter definitions and defaults'). This effectively distinguishes it from sibling tools like execute_adhoc_query and execute_query.

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 implies usage when a saved parameterized query exists, but it does not explicitly state when to use this tool over similar siblings (e.g., execute_query) or provide any prerequisites, when-not-to-use conditions, or alternative tool references.

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