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

Beyond the annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false), the description adds the tickets:read permission requirement, newest-first ordering, and the fact that retained baselines survive group deletion. These are concrete behavioral details an agent cannot infer from the annotations.

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?

Three terse sentences with the core action and scope front-loaded. Each remaining sentence adds a distinct fact: ordering, retention behavior, and permission. 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 no output schema and zero schema descriptions for three parameters, the description does not fully equip an agent to call the tool correctly: the meaning of root_id and the role of before_id/limit are missing. The permission and retention details are helpful, but the pagination and parameter gap remains.

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 should explain root_id, limit, and before_id. It only hints that the result is scoped to an owned delivery group, which likely maps to root_id, and leaves limit and before_id (pagination cursor) unexplained.

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 ('List'), resource ('saved baselines'), scope ('owned delivery group'), ordering ('newest first'), and a distinctive inclusion ('retained baselines after group deletion'). This clearly differentiates it from get_scope_baseline and compare_scope_baseline.

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 makes the intended context clear — retrieve baselines for an owned delivery group — and even notes the required permission. However, it does not explicitly mention sibling alternatives or when to prefer get_scope_baseline or compare_scope_baseline, so no exclusions are provided.

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