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

No annotations are provided, so the description fully carries the burden. It discloses critical behavioral traits: paid (150 credits), requires Authorization Bearer + sufficient balance, output is base64 PDF, and no basemap due to local units. This goes beyond typical descriptions. Not disclosing error behavior or idempotency is a minor gap, but the cost and auth warnings are particularly valuable.

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?

Every clause earns its place: cost warning, core function, examples, no-basemap limitation with alternative, auth requirement, and return structure. It is front-loaded with the most important fact (PAID) and remains compact. No filler or 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?

Given output schema exists, the description doesn't need to explain return values, but still does so concisely. It mentions the required auth and credit balance, which is essential for a paid tool. It also distinguishes from georeference_dxf and enough context to select this tool over many siblings. Missing a small note on the optional 'title' parameter's effect, but overall the description is quite complete.

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 coverage is 0%, so the description must compensate. It gives context about the 'dxf' parameter ('render a DXF drawing') but does not specify the exact input format (e.g., raw DXF content, file path, or base64). The optional 'title' parameter is not mentioned at all, though its default is in the schema. Partial compensation, but leaves ambiguity for one of two parameters.

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 opens with a specific verb+resource: 'render a DXF drawing to a one-page PDF site-plan report'. It clearly distinguishes itself from siblings like dxf_to_geojson and export_geojson_to_pdf by specifying the deliverable (site-plan report with vector plot, entity breakdown, layer list). It also gives example prompts, making the tool's purpose unambiguous.

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 explicit when-to-use guidance via examples ('make a PDF of this site plan'). It also explicitly tells the agent when NOT to use it: 'No basemap... use georeference_dxf first if you need a real-world-referenced report.' This direct exclusion and alternative are exactly what the dimension asks for.

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