get_model_offline

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

With no annotations provided, the description carries the full burden. It discloses a significant side effect ('a Desktop window appears') and clarifies the offline nature. It does not mention failure modes or file locking, but the key behavioral trait is well covered.

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 primary purpose, followed by the key side effect and relationship to a sibling. Every sentence 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?

Given the tool's complexity (opening Desktop, reading model, closing), the description covers the main side effect, the offline context, and the scope of what is read. It does not describe the output format, but since there is no output schema, this is a minor gap; overall it provides enough context for an agent to select and invoke the tool safely.

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 description coverage is 100% for both parameters, so the baseline is 3. The description adds the important nuance that the pbix must be 'CLOSED', but it does not add extra meaning for timeoutSec beyond what the schema already provides. The description adds minimal value beyond the schema.

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 reads the model of a closed .pbix and lists specific contents (tables, columns with data types, measures with DAX, relationships, named M expressions). It also distinguishes itself from the sibling get_model_summary by explicitly positioning itself as the offline form.

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?

It explicitly names the alternative (get_model_summary) and states when to use this tool ('no session / no manually-open Desktop'). However, it does not explicitly phrase a 'when not to use' condition, leaving the implication instead of a clear exclusion.

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