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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds substantially more: conditional behavior (new-model entries where the workspace has them, classic boards otherwise), a permission gate (Pro or trial workspace), and the fact that the response augments entries with the project's open_actions_count. That is real behavior beyond the structured hints.

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?

Purpose and scope are front-loaded in the first sentence, and the second sentence's field enumeration is dense but justified given there is no output schema. The semicolon-heavy run-on sentences slightly reduce readability, but no sentence 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?

With no output schema, the description compensates by enumerating the returned fields (uid, name, kind, status, date, stage, template, facilitator, action counts, url) plus the added open_actions_count, and it states the workspace requirement. Nothing an agent needs to call it correctly is missing.

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?

There is a single required parameter, project_id, and schema description coverage is 100%, so the schema fully documents it. The description adds no syntax, format, or constraint detail beyond what the schema already provides, which is the baseline-3 case.

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 and resource ('List a project's retrospectives') and immediately distinguishes two data shapes: new-model retrospectives/health checks versus classic retrospective boards. It names the sibling get_retrospective as the deeper alternative, so an agent can separate it from that tool without opening a schema.

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?

Routes the agent explicitly: 'Use get_retrospective for the full picture,' which is an effective when-to-use-this-instead signal, and states the eligibility prerequisite ('Requires a Pro or trial workspace'). It does not spell out a hard when-not condition, so it falls just short of the top tier.

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