create_level

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the creation action and parameter details, missing key information such as side effects (e.g., whether existing levels are affected), required permissions, failure modes, or implications for model state.

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 concise, front-loading the main purpose, followed by a brief explanation of levels' role, then a structured Args section. Every sentence adds value without unnecessary detail.

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 absence of an output schema, the description does not explain what the tool returns (e.g., a list of created level IDs), leaving the agent without expected response structure. Also lacks behavioral notes. For a creation tool, this is 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?

The input schema is sparse with a single array parameter 'levels' having extra properties allowed (0% coverage). The description adds needed meaning by specifying each element requires 'elevation' (float in mm) and optionally 'name', which is essential for correct invocation.

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 uses a specific verb 'Create' and clearly identifies the resource 'building levels (floor elevations)' in Revit. It explains what levels do and distinguishes this tool from siblings like list_levels, which only list levels.

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 states that levels 'must be created before placing walls, floors, or other level-dependent elements,' providing clear context for when to use this tool. It does not explicitly exclude alternative approaches or mention when not to use it, but the guidance is strong.

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