Update a collection

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

Annotations include idempotentHint=true, and description adds critical behavioral details: the tool reads first then merges to avoid removing collaborators, explains parent_id=0 behavior, and warns about is_public=true needing confirmation token. No contradiction with annotations. Minor gap: doesn't describe rate limits or reversal possibility.

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?

Three short, front-loaded paragraphs. Every sentence provides necessary context—no fluff. Uses bullet-like formatting with line breaks for readability. Perfect length for this complexity.

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?

Despite 7 parameters and no output schema, the description covers key behavioral aspects (merging, owner restriction, top-level move, public confirmation). Minor gap: does not describe return value or error cases, but acceptable given output schema is not required.

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 57%, and description significantly adds meaning: explains parent_id=0 behavior beyond schema, describes confirm_token purpose and usage pattern, clarifies is_public implication ('every link in it readable by anyone'). More details on color and description would be helpful.

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 'Changes a collection' and explains the behavior of non-provided fields, distinguishing it from create_collection or delete_collection siblings. It gives specific verb+resource pairing.

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?

Description provides clear usage context: who can use it (only owner), how to move to top level (parent_id=0), and confirmation token requirement for public visibility. However, it does not explicitly mention when to use this tool over alternatives like update_link or delete_collection.

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