Run Migration Eval

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal that the tool uses 'user-owned local provider credentials,' which is useful, but it does not say whether this operation executes provider calls, has side effects, incurs costs, requires special permissions, or how it behaves on failure.

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 one tight sentence with no waste and front-loads the main action. However, its brevity crosses from concise into under-specified, so it does not quite earn a 5.

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?

The tool accepts three complex nested objects and has no annotations, so the description leaves too much to inference. The presence of an output schema covers return values, but the lack of guidance on configuration structure, execution semantics, or credentials limits completeness.

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 by clarifying parameters. It does not explain what sits inside suite, source_config, or target_config, nor how they relate to one another. The parameter names alone are insufficient for three complex nested objects.

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 uses a specific verb 'Run' and names the object 'source and target,' but it does not clarify what 'source and target' actually are (models? configs? prompts?). The title 'Run Migration Eval' adds context, but the description alone does not clearly differentiate this tool from siblings like generate_eval_suite or compare_outputs.

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 when-to-use guidance, prerequisites, or alternatives. The only implicit hint is that this runs an evaluation with user-owned local provider credentials, but it does not explain when an agent should choose this over the many related sibling tools.

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