tcunit_results

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered and the bar is lower. The description usefully adds that a remote source is read 'over ADS' and that remote_path is the default, but it omits precedence rules when multiple sources are supplied and any ADS-connection prerequisites.

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 tight sentences with the core action front-loaded and the source enumeration second; no filler. The source list is compressed into a single clause, which is efficient though slightly dense.

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 values need no explanation, and annotations cover the safety profile. However, for a 3-parameter tool with 0% schema coverage and no required params, the definition does not resolve what happens if no source is given or how competing sources are prioritized.

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 description coverage is 0%, so the description must carry parameter meaning. It maps all three parameters to their sources (raw XML text, local file, file on target over ADS) and identifies remote_path as the default, but leaves precedence and mutual exclusivity between xml_text/local_path/remote_path unstated.

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 ('Parse') plus resource ('TcUnit xUnit result') and the concrete output ('pass/fail summary'), which is more precise than the bare name. It does not explicitly differentiate itself from the sibling tcunit_run (which presumably executes tests) or tcunit_scaffold, so an agent must infer the read/parse vs run distinction.

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 tells you what inputs are acceptable and that the remote path is the default, which implicitly frames when to use it (after a run, when you already have a result artifact). It gives no explicit when-to-use versus tcunit_run or guidance for choosing among the three sources, so usage is only implied.

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