update_collection

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

With no annotations provided, the description carries the full burden. It clearly indicates this is a mutation tool ('modifies', 'update'), but doesn't disclose important behavioral aspects like permission requirements, whether changes are reversible, error conditions, or rate limits. The description doesn't contradict annotations (none exist), but leaves significant behavioral context unspecified.

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?

Well-structured with clear sections: purpose statement, usage guidelines, parameters, and return value. Every sentence adds value, though the 'Args:' and 'Returns:' sections could be integrated more naturally. The description is appropriately sized for a 4-parameter mutation 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 mutation tool with no annotations and no output schema, the description provides good parameter semantics and clear purpose. However, it lacks important context about permissions, error handling, what 'refresh collection metadata' entails, and the format of the 'result message confirming update'. Given the complexity of a write operation, more behavioral transparency would be beneficial.

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 compensate. It provides meaningful context for all 4 parameters: collection_id is 'the collection ID to update', name is 'optional new name', description is 'optional new description', and color is 'optional new hex color code (e.g. #FF0000)'. This adds substantial value beyond the bare schema, though it doesn't explain format constraints beyond the color example.

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 the tool 'modifies an existing collection's properties' with specific examples (rename, update description, change color, refresh metadata). It distinguishes from sibling tools like create_collection (creates new) and delete_collection (removes), but doesn't explicitly contrast with update_document which modifies documents rather than collections.

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 provides explicit usage scenarios with bullet points (when you need to rename, update description, change color, refresh metadata). It implies this is for modifying existing collections rather than creating new ones, but doesn't explicitly state when NOT to use it or mention alternatives like create_collection for new collections.

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