create_drawing_from_model

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

No annotations are provided, so the description carries full burden. It only states the basic action without disclosing side effects, such as whether existing drawings are affected, if the previous drawing is closed, or what the output is. The description is too minimal to adequately convey behavioral traits.

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 very short (one sentence) and front-loaded with the action. However, it is under-specified, lacking essential details. It is concise in length but not in content, making it merely adequate.

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 the tool's complexity (2 parameters, no output schema), the description is insufficient. It does not explain the template parameter's purpose, sheet_size options, or the expected outcome. It misses contextual details like whether the model must be active.

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 input schema has 2 parameters with 50% description coverage (only template described). The tool description does not mention any parameters, thus adding no additional meaning. It fails to compensate for the schema's incomplete description of sheet_size.

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 the action: create a new drawing from the current 3D model. It specifies the verb 'create' and the resource 'drawing from the current 3D model'. However, it does not distinguish itself from sibling tools like 'create_drawing_vba' which might have a similar purpose.

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 usage guidelines provided. The description does not mention when to use this tool vs alternatives, nor does it specify prerequisites such as requiring an open 3D model or the model type (part/assembly).

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