migrate_collection

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Add, remove, or modify fields' implies a potentially destructive mutation operation, it doesn't disclose critical behavioral traits like whether this operation requires specific permissions, whether it's reversible, what happens to existing data during migration, or potential downtime implications. For a complex schema migration tool with zero annotation coverage, this is a significant gap.

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 extremely concise at just 7 words, front-loading the core functionality with zero wasted language. Every word earns its place by communicating the essential action and target.

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 complex schema migration tool with 9 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain the migration process, data preservation implications, error handling, or what happens to existing records during field modifications. The description should provide more context about this potentially complex and impactful operation.

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?

The description mentions 'fields' but doesn't elaborate on what 'Add, remove, or modify' means in terms of the 9 parameters. With 100% schema description coverage, the schema already documents all parameters thoroughly. The description adds minimal value beyond what's in the structured schema, meeting the baseline expectation when schema coverage is high.

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 action ('Add, remove, or modify fields') and the target resource ('from a collection'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from sibling tools like 'update_record' or 'create_collection', which might also modify collection structures in different ways.

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 no guidance on when to use this tool versus alternatives. With sibling tools like 'update_record' (for modifying individual records) and 'create_collection' (for creating new collections), there's no indication of when this schema migration tool is appropriate versus those other operations.

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