bulk_operations_wizard

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. It mentions 'safe execution' and 'Guides through,' hinting at interactivity and safety, but lacks details on permissions required, potential side effects, rate limits, or error handling. For a tool with admin tasks and no annotations, this is insufficient.

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 sized with three sentences, front-loaded with the main purpose. Each sentence adds value: starting the wizard, guiding safe execution, and listing supported operations. There's minimal waste, though it could be slightly more structured.

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?

Given the tool's complexity (admin tasks, interactive wizard), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks details on behavioral traits, parameter meanings, and expected outcomes, making it inadequate for safe and effective use by an AI agent.

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 for undocumented parameters. It doesn't mention any parameters like 'dry_run' or 'operation_type,' nor does it explain their purposes or usage. The description adds no semantic value beyond what the schema provides, failing to address the coverage gap.

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: 'Start the interactive Bulk Operations Wizard for admin tasks' specifies the verb (start), resource (wizard), and scope (admin tasks). It distinguishes from siblings by emphasizing interactivity and guidance, though it doesn't explicitly contrast with specific sibling tools like bulk_schema_update.

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 implies usage context through 'admin tasks' and 'safe execution of operations across multiple schemas,' suggesting it's for administrative bulk operations. However, it doesn't explicitly state when to use this tool versus alternatives like bulk_schema_update or bulk_schema_migration, nor does it provide exclusions or prerequisites.

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