update-contact-folder

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

The description adds the rename limitation and notes the default folder behavior, but does not explain why destructiveHint=true (e.g., effects of moving folder). Annotations already indicate mutation and destructiveness, so description adds only marginal 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?

The description is relatively concise with three sentences plus a tip. The tip is informative but uses formatting (emoji, code-like syntax) that may not be ideal. Front-loaded with purpose.

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?

Covers main purpose and key usage notes (rename, move, default folder limitation). However, it does not explain implications of moving a folder (e.g., effect on child folders or permissions). Utility parameters (includeHeaders, excludeResponse) are not mentioned, but that is acceptable given common usage.

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 high (75%), providing a baseline of 3. The description adds value by highlighting that displayName renames and parentFolderId moves, and warns about the default folder. This goes beyond the schema's property descriptions.

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 it updates a contact folder's properties and mentions specific writable fields (displayName, parentFolderId). It distinguishes from sibling tools like create-contact-folder and delete-contact-folder, though could be more explicit about the exact scope.

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 implies usage for renaming or moving folders and notes the default folder may not be renameable, but does not explicitly state when to use this tool vs alternatives like create-contact-child-folder. No when-not guidance provided.

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