find_pbix_files

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

With no annotations, the description carries the burden and does so well: it discloses that Power BI Desktop isn't required, what the default scan scope is, the env-var extension path, and that `truncated=true` means results were capped. It omits things like scan cost/duration or permission-error handling, keeping it just short of a 5.

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?

Front-loaded with the core action and the key qualifier, then defaults, then return shape. Dense and mostly waste-free, though the parenthetical return-field enumeration runs long for a tool with an output schema.

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 two-parameter discovery tool with an output schema and no destructive behavior, the description covers scope, defaults, overrides, and truncation semantics. An agent has everything needed to invoke it correctly without guessing.

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 is 0%, so the description must compensate, and it does: `search_dirs` is explained as an override of the default folders and `max_results` is tied to the `truncated` flag with guidance to raise it. Some detail (e.g., whether search_dirs replaces or adds to defaults, ordering semantics of max_results) is implied rather than stated.

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?

States a specific verb and resource ('Scan folders recursively for .pbix / .pbit files on disk') and an important scope qualifier ('no Power BI Desktop needed'). It is clearly distinguishable from every sibling, which are model/report analysis tools rather than disk discovery.

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 default behavior (Desktop, Documents, Downloads, OneDrive folders), how to extend it via POWERBI_MCP_SCAN_DIRS, and when to override with `search_dirs`. It doesn't name an alternative sibling to use instead, but none of the listed siblings overlap with file discovery, so context is effectively complete.

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