drawing_import_jww

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

No annotations are provided, so the description carries the full disclosure burden. It indicates a mutating import but says nothing about whether existing entities are merged or overwritten, whether the target drawing must already exist, permission requirements, or failure/duplicate behavior. For a write tool with zero annotation coverage this is a significant gap.

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 front-loaded sentence that leads with the action and resource, with the filter options parenthetically condensed. No waste, though the closing purpose clause is arguably padding rather than essential invocation info.

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 7-parameter mutation tool with no annotations, no output schema, and 0% schema coverage, the description is thin: it omits destination-drawing semantics, parameter formats, and any behavioral guarantees. An agent could not confidently invoke this without opening external docs.

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 7 parameters, so the description must compensate, but it only echoes the filter names (lg/ly/types/bbox) without explaining what lg or ly mean, what values 'types' accepts, or the bbox format. The tag, name, and path parameters receive no explanation at all — notably whether 'name' is a new or existing drawing.

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?

States a specific verb (Import) and resource (entities of a .jww file into a drawing) and even names the downstream purpose (edit, re-export, send back to Jw_cad). It is clearly distinguishable from siblings like jww_info/jww_query (read) and drawing_export (write-out), though it never names those alternatives explicitly.

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 'so they can be edited, re-exported or sent back to Jw_cad' clause implies the intended workflow, giving implied usage rather than explicit guidance. There is no statement of when NOT to use it, no prerequisites (does the target drawing need to exist?), and no named alternative such as scan_vector_import or jww_to_dxf.

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