export_draft_review_artifact

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds that it renders a 'unified draft review bundle' and supports an optional publication profile, which is useful context, but says nothing about auth needs, size limits, or side effects on the underlying draft.

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?

A single front-loaded sentence that leads with the action and resource, with no filler. Slightly jargon-dense ('unified draft review bundle') but efficient overall.

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 not be explained, but with 11 parameters at 0% schema coverage the description leaves most filtering/selection inputs undefined. For a multi-parameter export tool this is a meaningful completeness gap.

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% across 11 parameters, so the description must carry parameter meaning and largely does not. It only loosely gestures at format (markdown/json) and artifact_profile (publication-style profile); identifiers (cas, dtxsid, inchikey, version_id), limits (assay_limit, min_hitcall, stressor_limit), and draft_id are left undocumented.

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?

Names a specific verb (Export) and resource (draft review artifact) and clarifies it renders the unified draft review bundle in markdown or json. This is clear enough to distinguish it from save_draft_review_artifact and export_draft_replay_package, though it never explicitly names those siblings.

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 provides no when-to-use guidance, prerequisites, or exclusions relative to alternatives like save_draft_review_artifact, review_draft_bundle, or list_saved_draft_review_artifacts. Usage must be inferred from the name alone.

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