export

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

The description adds meaningful behavioral context beyond the annotations by specifying that the output is a self-contained directory and that it includes sections, documents, and catalog but excludes indexes. It does not cover overwrite behavior, permissions, or return status, but the idempotent/non-destructive annotations already establish the core safety profile.

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?

One tight sentence conveys the action, output type, inclusion set, and exclusion set without redundancy. The most important information is front-loaded and every part of the sentence earns its place.

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?

For a tool with one optional parameter and no output schema, this is close to complete: the destination and snapshot structure are clear, and annotations cover idempotence and safety. The only gaps are unspecified return/success behavior and whether the target path is created or expected to exist.

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 schema coverage is 100% and the single parameter path is explicitly documented with a default value. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 states a specific verb ('Export'), a clear resource ('the knowledge base'), and a concrete deliverable ('self-contained directory snapshot'), then enumerates what is included and excluded: 'sections, documents, catalog -- no indexes'. This clearly differentiates it from read/search/index-related sibling tools.

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 intended use is implied: call this when you want a directory snapshot of the knowledge base, not an index-aware operation. However, the description does not explicitly state when to use it versus alternatives, and none of the sibling tools are mentioned as alternatives or exclusions.

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