execute_dmv

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

With no annotations, the description carries the full burden. It discloses query constraints (no JOIN, GROUP BY, simple WHERE), supported rowsets, and the optional max_rows cap. It does not mention side effects or permissions, but for a read-only introspection tool this is acceptable.

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 well-structured: purpose, accepted format, rowsets, limitations, and parameter definitions. It is comprehensive without being overly verbose, though it could be slightly more concise.

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 output schema exists (so return values are documented), the description covers all necessary aspects: input parameters, usage guidelines, behavioral constraints, and relevant rowsets. It is fully sufficient for an agent to decide when and how to invoke this 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 0%, so the description must compensate. It clearly documents both parameters: 'query' as the DMV SELECT query and 'max_rows' as an optional row cap with default 0. This adds essential meaning beyond the raw 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 explicitly states it executes DMV queries for metadata introspection. It distinguishes from sibling tools like execute_query and list_metadata by specifying the DMV SQL format and target system rowsets.

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 details the accepted query format (SELECT ... FROM $SYSTEM.<rowset>), lists useful rowsets for different models, and notes SQL limitations. It provides clear context for when to use this tool but does not explicitly exclude alternatives.

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