List Drawing Templates

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

With readOnlyHint=true already covering the safety profile, the description adds genuine extra context: it 'never refuses' and reads a catalogue, and it discloses that `.dwt` twins only exist once built on a live AutoCAD with a specific script. That is a real behavioral precondition an agent would otherwise not know.

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?

Purpose is front-loaded in the first clause, and the field enumeration is dense but each item maps to a real column. The second half is somewhat heavily packed with backtick-delimited jargon, which costs a little readability.

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?

An output schema exists, so return values did not need describing, yet the description spends most of its length detailing row contents (standard, sheet, paper, layer_set, files.dxf/dwt flags). This is complete and non-misleading, but the emphasis is slightly misallocated toward schema-covered fields rather than usage.

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 tool takes zero parameters, so the baseline is 4. The description instead characterizes the catalogue rows returned, which is a reasonable substitute and does not misstate any input semantics.

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 states a specific verb and resource and ties the tool directly to its consumer: the templates `drawing_new(template=<name>)` can start from. An agent can distinguish it from the sibling `drawing_template_save` and `template_list` without opening any schema.

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?

It gives clear context for use ('the templates drawing_new can start from') and the assurance that it never refuses. It does not, however, explicitly name when NOT to use it or how it differs from the nearby `template_list` sibling, so a small amount of routing is left to inference.

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