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

Annotations already show readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds that the tool returns a read-only summary, includes text content, and notes skipped/unsupported types. No contradictions.

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?

Very concise single sentence that efficiently conveys the tool's purpose and usage. No wasted words; front-loaded with key action.

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?

Given the simplicity (1 param, no output schema), the description is complete: it describes the output contents in detail, explains the parameter with usage notes, and provides a clear use case. No gaps.

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?

The parameter 'source' is described with practical details: accepts URLs or inline DXF text, notes that local file paths are unavailable, and suggests an alternative local server. This adds significant value beyond the schema's description, which is already thorough (100% coverage).

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 clearly states it returns a structured JSON summary of a DXF drawing, listing specific contents (units, bounding box, layers, counts, text, unsupported types). It differentiates from siblings by focusing on structural questions without rendering an image.

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?

Explicitly states when to use: for structural questions (what layers, how many parts, size, text) and clarifies it does not render an image, implying alternatives like render_dxf. Does not explicitly name sibling tools, but context provides them.

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