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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered without the description. The description adds the content scope (layout, shared draft state, suggestions, releases), which is useful, but it does not disclose error behavior for an invalid policyId or access constraints, and much of the content list overlaps with the existing output schema.

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?

Two short sentences, front-loaded with the read scope and followed by the timing cue; nothing is padded. The terseness is appropriate even if the density of jargon ('workspace', 'frozen releases') leaves some ambiguity.

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 an output schema present, return values need not be explained, and annotations carry the safety profile, so the description need only cover scope and usage. It does that partially, but leaves the central 'policy workspace' concept and its relationship to get_policy undefined, which is the most likely source of mis-selection among siblings.

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 description says nothing about policyId, and schema description coverage is 0%, so no compensation for the gap occurs. Mitigating factor: there is exactly one parameter and its name is nearly self-documenting in the context of a policy tool, so the practical harm is limited rather than severe.

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 ('Read') applied to a composite resource and enumerates its parts: policy layout, shared draft state, tracked suggestions, frozen releases. That is more informative than a tautology. However, it never differentiates the 'workspace' from the sibling get_policy or list_policy_comments, so an agent cannot fully tell whether this supersedes or complements those 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?

The second sentence, 'Use before document workspace changes', gives a genuine timing cue that implies this is a read-prerequisite for mutation. But it offers no when-not guidance, no named alternatives, and no prerequisites (permissions, whether the policy must be in a draft state).

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