pbi_persist_now

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

Disclosures Win32 keyboard injection, only Ctrl+S, confirm requirement, env var prerequisite, polling with timeout, and immediate return without pbix_path. No annotations, so description carries full burden and does it thoroughly.

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?

Well-structured with sections, front-loaded purpose, efficient sentences, no fluff. Every sentence adds value.

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?

Covers purpose, prerequisites, parameter details, error handling, and behavior. Output schema exists, so return values not needed. Complete for complexity.

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 0%, but description explains each parameter: pbix_path (optional polling), confirm (must be True), timeout_seconds (clamped). Adds essential meaning beyond 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?

Clearly states the tool triggers Power BI Desktop save (Ctrl+S). Distinct from sibling tools; unique persistence action.

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?

Explicitly describes when to use (after TOM mutations) and provides hard gates (env var, confirm). Does not explicitly mention alternatives, but context implies usage.

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