civil3d_drawing

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

Annotations are absent, so the description must handle behavioral disclosure. It lists actions like 'save' and 'new' but does not explain side effects, required permissions, or error handling. The descriptions are minimal but cover the basic intent.

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?

The description is extremely concise, using one sentence and a list. It front-loads the purpose and lists actions efficiently with no wasted words.

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 multi-action tool with no output schema, the description provides minimal detail for each action. More context on the 'save' and 'new' actions (e.g., file paths, overwrite behavior) would be beneficial.

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 100%, so the baseline is 3. The description repeats the action names with brief explanations but adds little beyond the schema's own parameter descriptions.

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 'Manage the active Civil 3D drawing' and lists specific actions, making it distinct from sibling tools like civil3d_alignment or civil3d_corridor.

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?

No guidance on when to use this tool versus alternatives. For instance, if the user wants to work with an alignment, they would need to infer that civil3d_alignment is more appropriate.

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