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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that: no mention of pagination, result ordering, empty-list behavior, or access requirements, which is the context an agent would actually need.

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?

One short, front-loaded sentence with no redundancy or filler. It is concise to the point of under-specification, but nothing in the phrasing 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?

This is a low-complexity, single-parameter read tool with a fully documented schema and no output schema, so the definition is minimally adequate to invoke it correctly. It falls short on what the returned baselines look like and how they relate to the sibling baseline tools.

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 single parameter has full schema description coverage, so the schema already documents 'project_id'. The description only restates that the listing is project-scoped and adds no format hints or edge-case behavior, matching the baseline of 3 when the schema does the work.

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 states a specific verb and resource ('List baselines') scoped to a project, so the action is unambiguous. It does not distinguish itself from the sibling 'get_project_baseline' (single baseline retrieval) or clarify what a 'baseline' is in this domain.

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 guidance on when to call this versus 'get_project_baseline', which is the obvious alternative for retrieving baseline data. No prerequisites, no exclusions, no indication whether the project must be joined or owned first.

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