pbi_select_model

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

With no annotations, the description carries the full burden. It discloses the persistent side effect of selecting the active local model and explains the conditional port requirement. It does not cover error cases or the catalog parameter, but these are secondary for this simple tool.

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 short, front-loaded sentences in Spanish. The first sentence states the core purpose and the second provides the only essential conditional detail. Every phrase contributes.

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 covers the main selection behavior and port logic, which is most of what an agent needs for this low-complexity tool. However, it omits any explanation of catalog and does not clarify when to use this over other model-related tools. The presence of an output schema reduces the need for return-value documentation.

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 schema provides only bare names/defaults with no descriptions. The description adds meaningful semantics for port (optional if a single model, required if multiple, sourced from pbi_list_desktop_models), but it leaves catalog completely unexplained.

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 states 'Selecciona el modelo local activo para futuras operaciones,' which clearly identifies the action and its resource. It is distinguishable from list/open tools, but it does not explicitly contrast with those siblings.

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 gives concrete usage context: port is unnecessary when only one model is open, but required when multiple models exist, and it points to pbi_list_desktop_models for obtaining the port. It does not explicitly say when to choose this tool over alternatives.

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