import_pdf_as_underlay

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

With no annotations, the description carries the full burden of behavioral disclosure and supplies none of it: whether the file is read from disk or bytes, whether the received content is placed in modelspace or as a layer, what happens on failure, or whether existing underlays are affected.

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?

A single short clause is not conciseness here but under-specification – it is too brief to earn its place rather than trimmed of waste. There is nothing front-loaded because there is nothing to front-load.

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 three-parameter import tool with no annotations and no output schema, the description is completely inadequate; an agent cannot determine required inputs, expected return, or side effects from it.

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% across three parameters (path, content, encoding), and the description adds nothing about any of them. The relationship between path and content, the utf8/base64 enum meaning, and which parameters are actually needed are all left unexplained.

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 restates the tool name almost verbatim ("Import PDF_AS_UNDERLAY content"), adding only the filler word "content." It conveys that a PDF is imported as an underlay, but this is entirely derivable from the name and does not distinguish the tool from sibling importers like import_dxf or attach_raster_layer.

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?

There is no indication of when to use this versus other import tools, no prerequisites, and no mention of how it relates to attach_raster_layer or the raster-layer family. The agent must infer everything from the name.

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