set_partition_m

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

No annotations are provided, so the description bears full responsibility. It indicates a mutation via 'Replace' but does not disclose side effects (e.g., overwriting existing expression, impact on refresh), prerequisites, or reversibility, which is a significant gap for a write operation.

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?

A single sentence front-loads the verb 'Replace' and the object, followed by a brief clarifying example. There is no wasted wording, making it highly 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?

The description conveys the core purpose but lacks behavioral context. With no annotations, no output schema, and limited parameter explanation, it is minimally viable but does not cover side effects, return values, or prerequisites.

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 50%. The description adds context for 'table' and 'm' by framing them as 'a table's M partition expression' and connecting to 'new source data'. It does not elaborate on sessionId or beyond the schema's own descriptions, providing moderate added meaning.

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 specific action 'Replace' and the resource 'a table's Power Query (M) partition expression'. The example 'repoint a table at new source data' distinguishes it from sibling partition tools like list_partitions, refresh_partition, or set_partition_mode.

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 example provides a concrete scenario (repointing at new source data), implying when to use the tool. However, it does not explicitly state when not to use it or compare with alternatives, relying on the user to infer usage.

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