rhino_new_document

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

No annotations are provided, so the description must disclose behavioral effects itself. It does not mention that creating a new document changes the active document context or that unsaved work may be at risk. The only added behavioral detail is that it returns a dict.

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 main action is front-loaded and the template explanation is compact. The extra controller line and vague Returns statement add some noise, but the overall structure is still concise.

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 document-level tool with no annotations, the description is under-specified: it does not warn about losing unsaved work, clarify how the active document is affected, or distinguish when to use this instead of rhino_open. The output schema may cover the return value, but the missing side-effect context is significant.

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 description adds real meaning for the template parameter: it specifies a .3dm path and that an empty value creates a blank document. However, it also lists a 'controller' argument that is absent from the input schema, which is confusing and undermines the parameter guidance.

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 states a clear action and resource: 'Create a new Rhino document'. The optional template clause adds useful scope, and 'new' distinguishes it from sibling tools like rhino_open and rhino_open_file.

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 usage context is implied: use this when a new blank or template-based document is needed. However, there is no explicit guidance on when not to use it or how it relates to alternatives like rhino_open, rhino_revert, or rhino_document_summary.

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