bulk_schema_migration

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'preview and rollback capabilities', which hints at safety features, but doesn't clarify whether this is a destructive operation, what permissions are required, how errors are handled, or what the migration process entails. The description is too vague about actual behavior beyond basic functionality.

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 appropriately concise with three short sentences that each add value. It's front-loaded with the core purpose, followed by key features. There's no wasted verbiage, though it could benefit from slightly more structure to separate functionality from capabilities.

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 7-parameter migration tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'migrate' actually means operationally, what happens to existing schemas, how conflicts are resolved, what the output looks like, or how preview/rollback work. The description leaves too many critical questions unanswered.

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?

With 0% schema description coverage for 7 parameters, the description must compensate but fails to do so. It mentions 'pattern-based selection' (hinting at 'schema_pattern') and 'maintains schema IDs' (hinting at 'preserve_ids'), but doesn't explain the purpose of source/target contexts/registries or the dry_run parameter. Most parameters remain semantically undocumented.

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's purpose as migrating schemas between contexts or registries with pattern-based selection and ID preservation. It uses specific verbs ('migrate', 'maintains', 'includes') and identifies the resource ('schemas'), but does not explicitly differentiate from sibling tools like 'migrate_schema', 'bulk_schema_update', or 'bulk_schema_cleanup'.

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. It mentions capabilities like preview and rollback, but doesn't specify scenarios where bulk migration is preferred over single-schema migration ('migrate_schema') or other bulk operations. No prerequisites, exclusions, or comparison to siblings are provided.

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