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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it is the same seven writers as the Export panel, and incompatible format/source combinations are refused by name rather than answered with an empty file. That refusal contract is exactly the kind of non-obvious behavior an agent needs.

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 sentences, front-loaded with the action and the format set, with the panel/refusal framing second. The long mid-sentence enumeration of formats largely duplicates the schema enum, which is mild redundancy, but nothing is padded or buried.

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?

With an output schema present, return values need no explanation, and the schema fully documents the five parameters including the nested _subject. The description supplies the why-default and refusal semantics; only the relationship to the history/viewing siblings is left implicit. Adequate for a complex export tool with rich schema coverage.

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 100%, so the baseline is 3. The description goes further by explaining the default choice ('methods is the default because it is the panel's first row and the only one every source can produce') and the conditional refusal of format/sbol_syntax, which is meaning the schema enum alone would not convey.

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 precise verb+resource ('Write a construct's recorded build out as a document') and then enumerates the seven concrete output forms, so an agent knows exactly what it produces. Positioning it as 'the Export tab of the History & Provenance panel' differentiates it from the read-side history siblings like get_construction_history or history_protocol.

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 conveys when a given format applies and that unsupported formats are refused by name, which is useful operational guidance. But it never names an alternative tool or says when to export vs. view the history (e.g., versus get_construction_history), so usage is only implied rather than contrasted.

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