Extract All Text from DXF

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and side effects. The description adds that it extracts both TEXT and MTEXT, which is a minor detail, and does not disclose any additional behaviors such as output ordering or performance. Given the annotation coverage, this is acceptable but not rich.

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, front-loaded with the core action, and no extraneous details. The wording is efficient and each word contributes.

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 single-parameter, read-only tool with rich annotations and an output schema, the description is complete. It states what it does and when it's useful; the output schema will specify return values, so nothing critical 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?

Schema description coverage is 100% for the single parameter (file_path), and the description adds no additional parameter meaning. The schema already provides the description of file_path as an absolute path, so the parameter semantics are fully handled by 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?

Description states a specific action ('extract all TEXT and MTEXT entities') and resource, with a clear use case ('reading annotations, labels, title blocks, and notes'). It clearly distinguishes from siblings like dxf_get_dimensions or dxf_get_blocks, even without naming them.

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?

Provides context on when to use ('useful for reading annotations...') but does not explicitly list alternatives or when-not scenarios. An agent could reasonably infer this is the go-to for text, but there is no explicit exclusion of other tools like dxf_get_entities_by_type.

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