outliner-collection_rename

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, but 'Rename a collection' reveals nothing about side effects (e.g., whether the rename propagates to scene references), name constraints, error behavior, or reversibility. For a mutating tool, this is a significant disclosure 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?

At three words, the description is maximally concise and front-loaded with zero filler. However, this brevity borders on under-specification rather than efficient compression, since it adds almost no information beyond the tool name itself and the context signals show substantial gaps elsewhere that the description could have filled.

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 mutating tool with no annotations, no output schema, and 0% parameter description coverage, a single sentence is insufficient. The description does not explain what a 'collection' is in this domain, what identifier format is expected, or what happens to dependent data — context that sibling tool definitions or richer descriptions typically provide.

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 0%, so the description must compensate for the lack of parameter documentation, but it adds no meaning to either 'name' or 'collection'. Both parameters rely entirely on their schema titles, and the description offers no details about name format constraints, uniqueness requirements, or how collection identifiers are resolved.

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 ('rename') and identifies the resource ('a collection'), making the core intent immediately clear. However, it essentially restates the tool name in natural language and offers no differentiation from sibling tools like outliner-collection_create, outliner-collection_delete, or object-rename.

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 alternatives. No prerequisites, exclusions, or context is given, and the description does not reference sibling tools such as outliner-collection_create/delete or outliner-object_move that might be relevant alternatives.

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