rename_dataset

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

Despite no annotations, the description discloses that it mutates the workspace namespace but does not edit geometry or attributes, and requires a path inside PathGuard allowed root. This fully informs the agent of behavioral traits and constraints.

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 two sentences, front-loaded with the action and method, and each sentence adds essential information without redundancy.

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?

The description, combined with the schema and output schema (not shown), covers purpose, parameters, behavior, and constraints. It mentions mutation, no geometry changes, and PathGuard, making it complete for this tool.

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 does not add meaningful information beyond what is already in the input schema parameter descriptions. The schema itself provides detailed semantics for 'dataset' and 'new_name', so the description's contribution is minimal.

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 clearly states the verb 'rename' and the resource 'dataset', specifying it operates within the same workspace and is for intermediate feature classes, tables, or rasters. This distinguishes it from siblings like delete_dataset or describe_dataset.

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 description says 'Use this for controlled cleanup of intermediate...' providing a specific use case. It does not explicitly mention when not to use or provide alternatives, but the context implies it is the only rename dataset tool.

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