Rocky Create Selection

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

No annotations are provided, so the description carries the full behavioral burden. It only says 'Create' — it does not state whether the selection is added to the current project, whether existing selections are affected, what permissions or project state are required, or that this is a mutating operation.

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?

It is a single, front-loaded sentence with no wasted words, but it is under-specified rather than genuinely concise — brevity here comes at the cost of needed context.

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?

Although an output schema exists (so return values needn't be described), a creation tool with six optional parameters and no annotations needs more: preconditions, what the selection is used for in post-processing, and any effects on project state are all missing.

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 description coverage is 100%, so parameters like kind, size, center, and final_angle are already well documented in the schema. The description adds no semantic detail beyond what the schema provides, making the baseline 3 appropriate.

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 verb 'Create' and resource 'selection' are named, but 'selection process for post-processing' is vague about what a selection actually is in Rocky (a geometry region such as a cylinder or cube) and how it differs from siblings like rocky_create_surface. An agent gets the general idea but not a crisp, sibling-distinguishing definition.

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?

There is no guidance on when to use this tool versus rocky_create_surface or other geometry-creation siblings, and no prerequisites stated (e.g., whether a project must be open first). The post-processing mention is the only contextual hint.

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