wpf_export_test

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

With no annotations, the description carries the full burden and does substantial work: it discloses the output shape (file-name/content pairs), the exact difference between formats, that tests spawn a fresh app, and that recorded assertions verify outcomes. It omits auth requirements, filesystem overwrite behavior for the target directory, and any rate/performance notes, keeping it 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?

The purpose and format distinction are front-loaded, and each sentence carries operational information (artifacts, env vars, test behavior). It reads as a dense run-on with several clauses packed together, which slightly hurts scannability but wastes no words.

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?

There is no output schema and no annotations, so the description must cover both behavior and result format; it explains the returned file-name/content pairs and the downstream steps needed to use them. It is nearly complete for a one-param export tool, missing only edge cases such as directory-exists or missing-recording errors.

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 single 'format' param has 0% schema description coverage, so the description must compensate, and it does: it names both accepted values, marks 'xunit' as the default, and explains what each produces. Only the absence of an explicit enum/validation note in prose keeps it from a 5.

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 (Export) and resource (a stopped recording), and enumerates the concrete artifacts produced per format (runnable .NET 8 test project + workflow.json vs workflow.json only). An agent can distinguish this from siblings like wpf_record, wpf_replay, and wpf_report without opening any schema.

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 phrase 'a stopped recording' implies the prerequisite that a recording must exist and be stopped first, and the description walks through the post-export workflow (save files, set env vars, dotnet test). However, it never names an explicit alternative tool or states when NOT to use this versus wpf_replay/wpf_report, so usage context is clear but not fully bounded.

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