read_mashup_traces

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

With no annotations, the description carries the full burden and does well: it discloses the log location scope (all files in the window) and a meaningful limitation ('Request bodies aren't logged, so paging can't be proven'). It omits any mention of permissions or data-sensitivity implications of reading a %USERPROFILE% path, which keeps it from 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 dense with useful detail; nearly every clause carries information. The embedded path parenthetical interrupts the opening sentence slightly but remains valuable.

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?

An output schema exists, so return shape needn't be described, and the read-only nature is implicit. For a 2-parameter diagnostic tool the description covers scope, contents, and limits well; the only real gap is the unexplained `since_minutes` 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?

Schema coverage is 0%, so the description must compensate. It explains `instance` well (matching SharePoint list IDs to model queries), but `since_minutes` is never mentioned despite being the time-window control. One of two parameters is undocumented, so it lands at minimum-viable-plus.

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?

Specific verb ('Read') plus a precisely identified resource ('Power BI Desktop's own mashup-engine trace logs' at a concrete path), and it enumerates what the logs contain (request counts, HTTP failures, durations, folding-failure reports, crashes). The claim that it is 'the ONLY source of connector-level runtime evidence' clearly separates it from sibling analysis tools like analyze_sql_queries and diagnose_power_query.

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 gives explicit usage context: pass `instance` to tie SharePoint list IDs to this model's queries, and it warns that the logs cover every file opened in the window (so results may include other files). It does not name a sibling alternative or state a when-not-to-use condition, keeping it below a 5.

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