list_flow_baselines

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

Annotations include readOnlyHint=true, and the description adds that only completed jobs are listed and details the returned fields. This goes beyond the annotation by clarifying the scope and output, which is valuable for the agent.

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?

Four concise, purposeful sentences: action, returned fields, domain context, and an alternative tool. No redundancy and the key verb is front-loaded.

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 simplicity (one parameter, output schema present), the description covers purpose, returned data, domain meaning, and the creation workflow. No critical gaps identified.

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 schema already provides a full description for model_group_id ('UUID of the Flow model group'). The description echoes this without adding new constraints, formats, or examples, so baseline 3 applies.

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 lists completed baseline (unconstrained) generation jobs for a Flow model group, and specifies returned fields (job IDs, path counts, horizons, creation dates). This distinguishes it from siblings like list_flow_scenarios by the 'baseline' and 'unconstrained' qualifiers.

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?

Provides context that baselines are used for comparison with scenarios and explicitly points to generate_flow_paths for creating new baselines. This gives practical usage guidance, though it doesn't explicitly contrast with other listing tools like list_flow_scenarios.

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