Delete baseline

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

Goes well beyond the destructiveHint=true annotation: it discloses that selection falls back to the dynamic baseline, that only the snapshot is removed while project planning data stays intact, that portfolios are refused, and that the action is 'one undo step'. These are exactly the side effects and reversibility facts an agent needs.

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 short sentences, front-loaded with the action and consequence, each carrying distinct information (fallback, data preservation, sibling routing, portfolio restriction, undo). No filler.

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?

With annotations covering the safety profile and an output schema present, the description supplies the remaining behavioral context - reversibility, data impact, and environmental restriction - leaving nothing material for an agent to guess.

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 100% - the number parameter is fully documented as coming from rillsoft_baseline_list, which the description echoes. The description adds no syntax or format detail beyond the schema, 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?

States a specific verb (Deletes) and resource (a baseline), then distinguishes it from the sibling rillsoft_baseline_list for enumeration. An agent can immediately tell this is the removal operation versus create/select/list in the baseline family.

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?

Names the alternative (listing goes through rillsoft_baseline_list) and gives a clear when-not condition (refused in a portfolio, no baseline exists there). It lacks explicit guidance on when to delete versus re-select, but the routing to the relevant sibling is clear.

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