dxf_info

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful context beyond that: it operates without opening AutoCAD and reports a specific set of structural facts, though it doesn't discuss limits (e.g., very large files).

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?

Front-loads the purpose, then layers WHEN-TO-USE, parameters, and a concrete example in labeled blocks. Every line earns its place and nothing is redundant.

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?

An output schema exists, so return values needn't be detailed, and annotations cover the safety profile. Combined with the stated purpose, usage rule, parameter constraint, and runnable example, an agent has everything needed to invoke it correctly.

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%, so the description must carry the parameter meaning, and it does: path is the .dxf path constrained to 'pastas permitidas'. The worked example reinforces the expected format. It stops short of specifying path syntax or behavior on invalid/out-of-scope paths.

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 and resource ('Resume um DXF') and enumerates exactly what it reports (version, units, layers, layouts, blocks, dimension styles, extension), so an agent knows precisely what it returns. It also positions itself against siblings by being the entry point before any other dxf_* tool.

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 'QUANDO USAR' block gives a clear routing rule: use it first, before any other dxf_* tool, to confirm units and layer/layout names. It names the relevant alternative set implicitly but offers no explicit when-not-to-use case, keeping it short of a perfect 5.

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