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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds meaningful behavioral context beyond those annotations: percentages do not certify conformity, and the portal and this tool share the same persisted state, which warns the agent about consistency semantics.

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?

The description is three short sentences with no filler. The main scope is front-loaded, the caveat about percentages follows immediately, and the shared-state note earns its place by clarifying data freshness. Nothing extraneous appears.

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 tool with annotations already covering safety and idempotency, the description sufficiently explains what the response covers and adds two important interpretive caveats. Although no output schema exists, the content list is adequate for an agent to know what to expect.

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 100%, and the projectId parameter is already well documented in the schema with its source ('returned by list or create dossier') and an exclusion ('never a local path'). The description itself contributes no additional parameter-level detail, so the baseline of 3 applies.

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 opens with the specific verb 'Read' and names a concrete resource: the dossier workspace. It enumerates the exact contents (adaptive document inventory, four business layers, fields, responsible members, prepared/human-reviewed percentages, blockers), which clearly distinguishes this read tool from siblings like read_dossier_access or read_document_plan.

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 read-only verb and resource name make the general usage context obvious, but the description does not explicitly state when to prefer this tool over alternative read or inspection tools. There are no exclusions, alternate tool names, or conditions such as 'use X when you need a narrower view.'

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