export

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

No annotations are provided, so the description carries the full burden. It discloses the interactive confirmation step and the output file. However, it does not specify behavior when confirm=false (e.g., whether export is skipped) or whether the file is overwritten, which are important for a mutation-like export tool.

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?

Three concise, front-loaded sentences. The main purpose is stated first, followed by workflow and output path. No redundant words or repetition of schema content.

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 low complexity (2 optional params, no output schema), the description covers the essential aspects: purpose, interactive confirmation, and output. It lacks details on return values or error handling, but these are minor 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?

Schema coverage is 100% as both parameters have descriptions. The description adds minimal extra meaning beyond the schema; it reinforces that modifications are changes to tickets and confirm is for a confirmation step, but does not clarify detailed usage (e.g., how modifications are applied).

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's function: 'Exportiert die finalen Tickets als JSON' (exports final tickets as JSON), with a specific output file. This distinguishes it from sibling tools inspect and plan.

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 use after finalizing tickets, as it mentions showing an overview and asking for confirmation. However, it does not explicitly state when to use this tool instead of alternatives like inspect or plan, nor any exclusions.

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