fabric_run_table_maintenance

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

With no annotations provided, the description must fully disclose behavioral traits. It identifies the operation as 'long-running' but fails to mention other critical aspects like blocking nature, required permissions, side effects on other operations, or expected duration. This leaves the agent with insufficient information to manage expectations.

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 sentence of 12 words, immediately conveying the core action and scope. It is front-loaded and contains no filler, making it optimally concise for quick parsing by an AI agent.

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?

Despite having no output schema and no annotations, the description omits essential context such as how to monitor progress, error handling, or what the return type is. For a complex, long-running operation, this is a significant gap that limits the agent's ability to use the tool appropriately.

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?

The input schema descriptions cover all 7 parameters at 100% coverage, so the baseline is 3. The description adds no additional parameter meaning beyond 'long-running' context, which does not enhance understanding of individual parameters.

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 verb 'Run' and the resource 'table maintenance' with specific operations (OPTIMIZE, V-Order, VACUUM) on a lakehouse table. It is distinct from sibling tools which mostly deal with CRUD or other execution tasks, making the purpose unmistakable.

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 no guidance on when to use this tool versus alternatives, such as other maintenance or run-type tools. It only notes that it is 'long-running' but does not specify prerequisites, typical scenarios, or exclusion criteria.

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