create_line_based_element

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It mentions batch creation and units, but it does not disclose required document state, permissions, side effects, error behavior, or whether any return value is produced. For a mutating tool, this is a notable 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?

The description is two sentences and directly introduces the tool's purpose, key capabilities, and units. There is no filler or redundant repetition of schema details.

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?

The schema is detailed and the purpose is clear, but the description omits important execution context such as requiring an active Revit document, how elements are added to the model, and any result or feedback after creation. Since there is no output schema, some of this burden falls on the description, leaving it slightly incomplete.

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% with descriptions for all parameters, so the baseline is 3. The description adds meaningful value by stating that all units are in millimeters, which is critical for correctly interpreting coordinates and dimensions not specified in the schema.

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') and the specific resource ('line-based elements in Revit such as walls, beams, or pipes'), which distinguishes it from sibling tools like create_point_based_element and create_surface_based_element.

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 description gives clear context for when to use the tool by defining line-based elements with examples, but it does not explicitly mention when not to use it or name alternative tools. The sibling context makes the distinction obvious, so this is a 4 rather than a 3.

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