export_bundle

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

The description includes a [WRITE][risk=medium] prefix, indicating it is a write operation and the risk level, which adds transparency beyond the schema. However, it does not detail permissions, side effects, or whether files are overwritten.

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 description is extremely concise: one sentence plus a clean arg list with no unnecessary words. Every element earns its place, and it is front-loaded with the risk indicator.

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?

Given the tool has no output schema and no annotations, the description covers purpose, parameters, and risk level adequately. It does not specify return values or overwrite behavior, but it is sufficient for a simple export tool.

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?

With 0% schema description coverage, the description fully explains all three parameters: bundle_path (path to bundle JSON), fmt (formats), and out_path (output path with default). This adds significant meaning beyond the schema's titles and defaults.

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?

The description clearly states the tool renders a bundle to specific formats (markdown/csv/json), with a specific verb and resource. This distinguishes it from sibling tools like verify_bundle or sign_bundle, which have different purposes.

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 implies the tool is for exporting bundles, but it does not explicitly state when to use it versus alternatives like verify_bundle or sign_bundle. No when-not or exclusions are provided.

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