catia_export

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the mutation/safety profile is partly covered, and the description adds the format surface. However, it omits key export behavior: whether an existing target file is overwritten, whether the output directory must pre-exist, and whether export modifies the live document. The listed

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, zero waste, with the core action front-loaded and the format enumeration kept compact. Nothing needs to be cut.

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 no output schema, the description should carry more of the burden for an export tool. It never says what is returned (success flag, written path, error behavior), nor how it handles overwrites or missing directories, and it advertises PDF which the format enum does not contain.

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 100% and both parameters are fully documented, including the enum and the extension-overrides-format rule, so the baseline is 3. The description's format list merely restates part of the enum, adding no syntax or precedence detail beyond the schema.

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 specific verb (export), a specific resource (the active document), and a destination (a file), then enumerates the supported formats. An agent can distinguish it from catia_save_document (which persists the native document) without opening either schema.

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?

Usage is implied by 'active document' and the format list, but there is no explicit guidance on when to use this versus catia_save_document or catia_drawing_export_pdf, and no prerequisites (e.g., an active document must exist). No when-not guidance or alternatives are named.

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