guided_context_reorganization

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

No annotations are provided, so the description carries the full burden. It mentions starting a workflow but doesn't disclose behavioral traits such as whether this is a long-running operation, what permissions are required, if it's interactive or automated, or what happens to existing schemas. The description is too vague for a workflow tool with potential side effects.

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 a single, efficient sentence that directly states the tool's action. It's front-loaded with the key verb 'Start' and avoids unnecessary words. However, it could be slightly more informative without losing conciseness.

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 complexity of a workflow tool (likely involving schema reorganization across contexts), the description is minimal. No annotations are provided, but an output schema exists, so return values are covered. However, the description lacks details on workflow behavior, prerequisites, or outcomes, making it incomplete for safe and effective use.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. A baseline of 4 is given since the schema fully covers the lack of parameters, and the description doesn't need to compensate.

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 states the tool 'Start[s] the Context Reorganization workflow for reorganizing schemas across contexts', which provides a clear verb ('Start') and resource ('Context Reorganization workflow'). However, it doesn't distinguish this from sibling tools like 'guided_schema_migration' or 'guided_schema_evolution', which also appear to be guided workflows. The purpose is understandable but lacks sibling differentiation.

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 doesn't mention prerequisites, when this workflow is appropriate compared to other bulk operations or guided workflows in the sibling list, or any exclusions. The user must infer usage from the name alone.

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