fabric_delete_semantic_model

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

Description says 'Destructive' which is already indicated by the destructiveHint annotation. No additional context about side effects (e.g., orphaned reports, permission requirements) beyond the annotation.

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?

Two short sentences with no fluff. However, 'Destructive' is redundant with the annotation, so the second sentence could be omitted. Still, overall efficient.

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?

Adequate for a simple delete operation given annotations and schema. Lacks information on synchronous behavior, error responses, or whether the operation requires specific permissions. Not insufficient 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 100% with clear descriptions for both parameters. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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?

Clearly states the verb 'Delete' and the specific resource 'semantic model', distinguishing it from sibling delete tools like fabric_delete_dataflow or fabric_delete_warehouse.

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?

No guidance on when to use this tool, prerequisites (e.g., model must exist), or alternatives. Does not mention checking existence via fabric_get_semantic_model or warn about irreversibility.

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