gdrive_rename

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses the dry_run behavior ('Preview the rename without committing it'), which is a meaningful behavioral trait. It also implies that file_id is preferred when known, which is useful operational context. However, it doesn't mention whether the rename is reversible, whether it requires specific permissions, or what happens if both file_name and file_id are provided. Still, the dry_run disclosure and the file_id preference add real value beyond the schema.

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 compact and well-structured. It front-loads the core purpose, then provides discovery guidance, usage boundaries, a dry_run note, and parameter explanations. Every sentence earns its place, and the structure makes it easy for an agent to scan. The 'Use this for' / 'Not for' pattern is particularly effective.

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 tool has 4 parameters, no annotations, and no schema description coverage, so the description must be thorough. It covers the core purpose, discovery prerequisites, the alternative tool, the dry_run behavior, and all parameters. The output schema exists, so return values don't need to be explained. The only minor gap is the lack of explicit precedence rules when both file_name and file_id are provided, and no mention of error conditions (e.g., file not found). Overall, it is nearly complete for an agent to invoke correctly.

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 schema's lack of parameter documentation. The description lists all four parameters (file_name, new_name, dry_run, file_id) and adds meaning: file_name is 'Current name of the file to rename', new_name is 'New name for the file', dry_run is 'Preview the rename without committing it', and file_id is 'Optional stable file ID (preferred when known)'. This is a strong compensation for the schema's bare titles, though it could be even more explicit about the relationship between file_name and file_id (e.g., which takes precedence).

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 opens with a clear verb and resource: 'Rename a file in Google Drive.' It explicitly distinguishes itself from moving a file to a different folder and names the sibling tool gdrive_move. This makes the tool's purpose unambiguous and easily differentiated from siblings.

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 provides explicit guidance: run gdrive_list_folder or gdrive_search first to obtain file_name/file_id values. It also states when to use this tool ('renaming files in place') and when not to ('moving a file to a different folder — see gdrive_move'). This is exactly the kind of when/when-not/alternatives guidance that helps an agent select the right tool.

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