dxf_export_pdf

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 useful behavior: lines/text remain vector, infinite zoom, page_size 'auto' adapts to the drawing bounding box, and background accepts colors. However, it omits critical mutation details such as whether it overwrites an existing pdf_path, error behavior, or required permissions.

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 front-loaded with the purpose, then uses a compact Args list. Every sentence adds value without repetition.

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 simple file-export tool with no output schema and no annotations, the description covers purpose and all parameters. It is mostly complete, though it omits sibling routing and overwrite/error behavior that would be useful for safe invocation.

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 0%, but the description compensates by documenting all four parameters: path as source DXF, pdf_path as output, background with 'white'/'black'/'dark' or #RRGGBB, and page_size with 'auto' (bounding-box adaptive) or A4/A3/A2 landscape. This adds complete parameter meaning beyond the schema's titles.

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 ('DXF 为矢量 PDF') with output characteristics, but it does not name or differentiate against siblings such as dxf_render or dxf_open_in_autocad. An agent can infer the tool exports to PDF, but explicit sibling contrast is absent.

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 parenthetical '适合打印归档' gives a use case, but there is no explicit when-to-use guidance, no when-not conditions, and no mention of alternatives like dxf_render. Usage is only implied by the printable/archival framing.

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