catia_drawing_export_pdf

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

The description discloses useful behavior such as file existence checking, optional PyMuPDF verification, return fields, and overwriting an existing file. However, overwriting an existing file contradicts the destructiveHint=false annotation, which claims only additive updates. This is an annotation contradiction.

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 compact and front-loaded, starting with the core action. Each sentence adds operational value: checks, return shape, and overwrite note.

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 two-parameter export tool with no output schema, the description supplies return fields, verification behavior, and overwrite behavior. It is nearly complete for invocation, though it lacks sibling routing guidance and the overwrite/destructiveHint conflict is misleading.

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 already 100%, and the description adds no parameter-level semantics beyond what the schema documents. The path and drawing parameters are fully described in the schema, so the baseline 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 and resource: export the drawing to a vector PDF, and even names the underlying API. It distinguishes the operation from generic export/screenshot siblings by specifying vector PDF output.

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 context is implied by the PDF export purpose, but there is no explicit guidance on when to use this instead of siblings like catia_export, drawing_render, or drawing_overlay. No when-not conditions are given.

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