rename_item

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention side effects, whether existing names are overwritten, whether authentication tokens are required, or what happens on failure. The only behavioral hint is 'repo token: folders only,' which is terse and ambiguous. This is insufficient for a mutation tool with eight parameters.

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 a single, front-loaded sentence with no filler. It communicates the core operation clearly. However, it is almost too sparse for a tool with eight parameters, so it is concise but not optimally structured for an agent's needs.

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 high parameter count, missing annotations, and no output schema, the description is not complete enough. It leaves unclear how tokens relate to file versus folder operations, what path semantics are expected, and how this interacts with sibling operations. The one parenthetical hint is not enough context for reliable invocation.

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%, and the description does not explain the meaning of path, new_name, is_dir, repo_id, or the various token parameters. It only mentions file/folder and repo token indirectly, which adds almost no value beyond the raw schema. An agent cannot confidently populate parameters from this description alone.

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 specific verb and resource: 'Rename a file or folder.' This clearly identifies the operation and distinguishes it from sibling tools like move_item or copy_item, since renaming is a distinct action. The parenthetical '(repo token: folders only)' adds a scope constraint but is somewhat cryptic and could confuse agents.

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. The description does not mention that move_item/copy_item should be used for moving or duplicating, nor when to choose directory renaming over file renaming. The parenthetical is a constraint, not a usage recommendation, so an agent is left to infer the appropriate context.

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