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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real value beyond them by enumerating the returned content set, warning that the percentages 'do not certify conformity', and disclosing that state is shared with the portal.

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?

Three sentences, front-loaded with the content inventory so the agent sees the scope first. The conformity caveat and shared-state note both earn their place; no filler.

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 must sketch the return shape, and it does list the content categories (inventory, layers, fields, members, percentages, blockers). Combined with annotations covering the read-only profile, this is nearly complete; only the exact output structure and pagination/limits are unstated.

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 coverage is 100% and the single projectId parameter is fully documented in the schema, including its pattern and the warning that it is a project/mapping ID, never a local path. The description adds nothing about parameters, so the baseline 3 is appropriate.

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?

Clear read verb plus the specific resource (dossier workspace), and it enumerates exactly what the read returns: adaptive inventory, four business layers, fields, members, percentages and blockers. It does not name or contrast with any sibling, so an agent must still infer its place among the many read_* tools.

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, when-not-to-use, or alternative guidance. 'The portal and this tool share the same persisted state' is a consistency note, not usage direction, and no sibling such as read_dossier_access or read_dossier_references is mentioned as a contrast.

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