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

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds beyond those: the auth requirement ('Requires tickets:read'), the 'frozen' and 'owned' characteristics of the baseline, and the meaningful limitation that older schema1 dates remain unknown.

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?

Two sentences with no filler. The action and resource are front-loaded, and both the auth requirement and data limitation are packed into the second sentence efficiently.

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?

For a single-parameter, read-only tool with strong annotations, the description covers the core invocation needs: what it reads, what permissions are required, and a key caveat. It is slightly incomplete because it does not explain how to find/choose a baseline_id, but this is minor given the tool's simplicity.

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 carries the burden of explaining baseline_id. It only mentions 'an owned baseline' without clarifying what baseline_id identifies, how to obtain it, or how it relates to owned baselines. This is insufficient compensation for the missing parameter documentation.

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 ('Read') and names a clear resource: 'frozen structural scope, estimates and captured explicit plans for an owned baseline.' The singular 'an owned baseline' semantically distinguishes this from sibling tools like list_scope_baselines 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 does not provide when-to-use guidance or mention any sibling alternatives. It gives no exclusions or routing cues beyond the basic read intent. 'Older schema1 dates remain unknown' is a data limitation, not guidance on choosing between tools.

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