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

Beyond the read-only, idempotent, non-destructive annotations, the description adds substantial operational context: record/character limits, block level depth, unit declaration behavior, truncation warnings, potential missing definitions, runtime, price, and a prompt-injection caution. None of this contradicts the annotations.

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 purpose is front-loaded and the description is dense with useful constraints rather than filler. However, several fragments are compressed awkwardly ('Returns extracts text...', 'Failures not charged..'), which slightly reduces readability.

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 read-only extraction tool with an output schema, the description covers the important input limits, output-characteristics warnings, exclusions, runtime, and pricing. A few phrases, such as 'definitions may not be displayed,' remain somewhat opaque, but no critical calling information is missing.

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?

There is only one parameter and schema description coverage is 100%; the schema already documents 'One ASCII or binary DXF, base64 encoded; at most 10 MB decoded. No DWG or ZIP.' The description repeats the same constraints but does not add meaningfully deeper parameter semantics 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?

The first sentence gives a specific verb and resource: 'Extract DXF text and block attributes.' It also scopes the input to one inline ASCII/binary DXF and explicitly excludes DWG, rendering, OCR, and takeoff, which clearly distinguishes it from adjacent PDF/document extraction siblings.

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 description gives clear usage context and exclusions: one inline ASCII/binary DXF, 10 MB max, no DWG or ZIP, and no rendering/OCR/takeoff. It does not explicitly name alternative tools for unsupported cases, so it falls short of a full when-to-use-vs-alternative guideline.

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