set_query_buffer

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

With no annotations, the description carries the full burden and does well: it states the action (wrap in Table.Buffer), the effect (loads once, stops re-evaluation and downstream folding), and the implementation detail (appends to M query). It lacks caveats like stale data or memory impact, but covers the core behavior.

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 key idea ('Power Query folding hint') and then a specific action. Every word earns its place, with no redundancy.

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?

The description covers the tool's action and effect, but lacks parameter semantics (3 params, low schema coverage) and any mention of prerequisites or side effects. It is adequate for a simple mutation but has gaps.

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 only 33% (only partitionName has a description), and the description adds no parameter details. It references 'the table' but doesn't explain sessionId or partitionName. The description fails to compensate for the low schema coverage.

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 tool wraps a table in Table.Buffer, with a specific verb ('wrap', 'appends') and resource ('the table's M query'). It also explains the purpose ('loads once into memory') and distinguishes it from related tools like set_stop_folding.

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 clear context: it is a 'Power Query folding hint' that stops re-evaluation and downstream folding, implying when to use it. It does not explicitly mention alternatives or exclusions, but the context is sufficient.

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