rename

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

With no annotations, the description carries the full behavioral burden for a mutation tool. It says nothing about whether the rename is reversible, whether renaming a folder affects the paths of contained items, whether missing items error out, or what permissions are needed. The item-format note is the only added context.

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?

Two short sentences, with the core action front-loaded before the argument hint. The 'item = folder path + title' phrasing is terse almost to the point of ambiguity, but nothing is wasted.

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?

Return values are covered by the output schema, but for a two-required-parameter mutation with no annotations the definition is thin: no effect-of-rename semantics, no prerequisites, and only half the parameters get any explanation.

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 coverage is 0%, so the description must compensate. It usefully clarifies that 'item = folder path + title'—a non-obvious construction an agent would not derive from a bare string field—but says nothing about the format of new_title (extension handling, length limits, uniqueness).

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?

States a specific verb (rename) and names the two resources it operates on (link, folder), which separates it from siblings like mkdir, trash, and sort. However it never distinguishes itself from 'move', which could plausibly also rename, so sibling differentiation is incomplete.

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 statement of when to use rename versus move (which likely relocates an item) or any other sibling. The only guidance is an implicit note on how to construct the item argument, which is parameter help rather than usage guidance.

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