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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value with "owned" (caller-scoped access) and by enumerating returned fields, but says nothing about what happens when the baseline is missing or not owned.

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?

A single front-loaded sentence with the verb first and no filler. It is telegraphic to the point of being slightly compressed ("approval/version" reads as shorthand), but nothing is wasted.

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 one-parameter read with no output schema, the description usefully enumerates the returned fields, which is exactly what the agent needs to decide relevance. It is only incomplete on error/precondition behavior for unowned or nonexistent baselines.

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?

Only one parameter and schema description coverage is 0%, so the schema contributes just the title "Baseline Id". The description's "owned baseline" implies the id must reference a baseline the caller owns, which is useful but falls short of documenting format or failure behavior for an invalid id.

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?

Names a specific verb (Read) and resource (baseline reference-file) plus the exact fields returned: fingerprint, row count, approval/version. That distinguishes it from approve_quality_baseline and draft_quality_baseline, which mutate state, though it never names those siblings explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The word "owned" hints at an access-scope precondition, but an agent must infer from the sibling names alone that it should call this rather than get_quality_report or get_quality_contract.

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