create_sheet

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

No annotations provided, so description must cover behavioral traits. It mentions optional parameters and defaults, but does not disclose potential conflicts (e.g., duplicate sheet numbers), error conditions, permissions required, or side effects. Lacks transparency for a creation tool.

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?

Well-structured with a clear opening sentence and an args section. Some redundancy ('Views can be placed on sheets after creation' could be integrated), but overall efficient and easy to parse.

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?

Does not describe return values (e.g., sheet ID) or confirmation of creation. No mention of error handling or prerequisites. For a creation tool without output schema, this leaves a significant gap in completeness.

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?

Adds meaning beyond the schema by providing examples and explanations for each parameter (e.g., sheet_number as 'e.g. A101', sheet_name default). However, does not clarify valid values for title_block_name or constraints, leaving some ambiguity.

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?

Clearly specifies the verb 'create' and resource 'drawing sheet in Revit for construction documentation'. Provides context on what sheets are and that views can be placed later, distinguishing it from sibling tools like create_view or create_detail_line.

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?

Implies usage for construction documentation and mentions that views can be placed afterward, but does not explicitly state when to use this tool vs alternatives like create_view. No 'when not to use' guidance, leaving the agent to infer from context.

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