update-contact-folder

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

Annotations already set destructiveHint: true and readOnlyHint: false. The description adds valuable context: it warns that the default 'Contacts' folder may not be renameable and clarifies which fields are writable. No contradiction with annotations.

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 concise—two sentences and a tip. It is front-loaded with the main purpose and every sentence adds value. No unnecessary fluff.

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?

Given the tool's complexity (4 params, nested objects, no output schema), the description covers updatable properties, a limitation (default folder rename), and a prerequisite. It lacks mention of the response or success indication, but overall it is adequately complete for an agent to use 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 coverage is 75%, so baseline is 3. The description goes beyond the schema by providing concrete examples for body parameters ('displayName?: 'New name'', 'parentFolderId?: '<id>'') and explicitly stating both are writable, which helps the agent understand usage.

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 'Update the properties of contactfolder object' and specifies the action as 'Updates a contact folder'. It distinguishes itself from sibling tools like create-contact-folder and delete-contact-folder, and even provides specific details on updatable properties (displayName, parentFolderId).

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 the tool is for updating an existing contact folder and gives a prerequisite ('Get the folder id via list-contact-folders'). However, it does not explicitly contrast with alternatives (e.g., create/delete) or provide when-not-to-use guidance, though the context is clear.

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