todo_rename_list

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

Annotations already disclose readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is known. The description adds nothing beyond that: it says nothing about permission requirements, what happens if list_ref matches nothing, or how ambiguity between identically named lists is resolved.

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, front-loading the action and then the key parameter nuance. Every word earns its place with no filler.

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 two-parameter mutation with no output schema and zero schema coverage, the description covers the purpose and the ambiguous parameter but leaves error behavior, permission needs, and name-collision handling unaddressed. Adequate to invoke, not fully complete.

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 carry the parameter burden. It does clarify the non-obvious list_ref ('list ID or its exact name'), but says nothing about new_name beyond what the title implies and gives no guidance on exact-name matching rules or name collisions.

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 and resource ('Rename a To Do list') and the 'To Do' qualifier separates it from the planner_rename_plan and planner_rename_bucket siblings. An agent can identify exactly what this tool does without opening the schema.

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?

Gives no when-to-use context, no prerequisites, no exclusions, and never mentions the neighboring rename or list-management tools (todo_create_list, todo_delete_list, planner_rename_plan). Usage is left entirely implicit from the tool name.

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