import_tmdl

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

With no annotations, the description carries full behavioral disclosure. It explicitly warns that applying REPLACES live model metadata (createOrReplace semantics), and that dry-run changes nothing. Also discloses auto-detection of PBIP definition subfolder.

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?

Three sentences, front-loaded with purpose, with important warnings in caps ('DEFAULTS TO A DRY RUN', 'changes NOTHING'). Every sentence earns its place without fluff.

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 lacking an output schema, the description covers purpose, input flexibility, destructive behavior, and the dry-run return value (table/measure diff). Complete for a complex import tool with no annotations.

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?

Adds meaning beyond the schema for folderPath by explaining it can be a model TMDL folder or a PBIP SemanticModel with auto-detection. Also clarifies applyToLiveModel's gating and createOrReplace semantics. SessionId is not described but is a common session parameter.

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 'Import a TMDL folder' into the live model with a specific verb and resource. The phrase 'official deserializer' adds context, and it distinguishes from siblings like export_tmdl by focusing on import.

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?

Explains that the tool defaults to a dry-run diff and that applying requires applyToLiveModel:true, guiding when to use it for preview vs apply. It doesn't explicitly name alternative tools, but the context is clear enough for sibling differentiation.

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