pbi_disable_auto_date_time

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

The description discloses the concrete side effect: disabling will cause Power BI to remove automatic date tables (LocalDateTable_*) on reopening the .pbip. With no annotations provided, this behavioral info is essential and well-stated, though it doesn't mention reversibility or exact timing.

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 clearly deliver the key information without redundancy. The structure front-loads the main action and then adds context.

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?

For a simple toggle tool, the description provides the essential context: what it does, when it applies, and a key side effect. The existence of an output schema reduces the need to document return values; the main gap is the undocumented 'request_id' parameter.

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 description only indirectly explains 'enabled' via 'Activa/desactiva', and does not mention 'request_id' at all. Since schema has no descriptions (0% coverage), the description should compensate for both parameters but fails to do so.

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 uses a specific verb 'Activa/desactiva' with a clear resource 'Auto fecha y hora' and scope 'solo modo pbip'. It clearly labels the tool's function and distinguishes it from sibling tools focused on model queries and report edits.

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 text explains the benefit of disabling ('aligera el modelo') and prerequisite ('Requiere proyecto .pbip activo'), plus limitation 'solo modo pbip'. It does not explicitly name alternatives, but provides sufficient context for when to use this tool.

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