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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description's 'change' aligns with a mutation. The description adds the specific scope (name/icon) but doesn't disclose any additional behavioral traits like reversibility, ownership requirements, or error conditions. It adds some value but doesn't go beyond the annotation basics.

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?

A single, concise sentence that front-loads the action and object. No wasted words, and it's appropriately sized for a simple update tool.

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 simple update operation, the schema covers parameters and annotations provide basic safety info. The description doesn't explain return values (no output schema) but that's not required. It doesn't mention prerequisites or side effects, but given the low complexity, it's largely complete. The only minor gap is the lack of explicit 'document collection' terminology, which is a clarity issue rather than a completeness one.

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 100%, so all parameters (collection, name, icon) are already documented. The description mentions 'name or icon' but doesn't add semantic detail beyond the schema. It doesn't clarify how the collection parameter works or that both fields are optional. Baseline 3 is appropriate.

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 states a clear action ('Change the name or the icon') and a resource ('folder'). While 'folder' is a synonym for 'document collection', it's slightly imprecise given the tool name and siblings (e.g., create_doc_collection). It distinguishes from update_doc, update_issue, etc. by resource type, but the wording could be more precise.

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?

No guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, exclusions, or sibling tools. For instance, it doesn't clarify that it's specific to document collections or when to use create_doc_collection instead. The one-liner simply states the action without contextual routing.

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