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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description does not contradict this. The description adds no behavioral details beyond the resource name, such as response form or absence of site mutation, but this is a simple read operation.

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 a single short sentence that front-loads the verb and resource with no redundant wording. It is appropriately sized for a one-parameter read operation, though it carries minimal substance.

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 simple getter with one documented parameter and read-only annotations, the description is minimally sufficient. However, with no output schema, it does not clarify what form the returned document takes, such as text, URL, or structured object, which could be useful for correct invocation.

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 input schema fully documents the single site_id parameter with 100% coverage, so the description does not need to compensate. The phrase 'for a site' loosely maps to site_id but adds no format, requiredness, or example beyond what the schema already provides.

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 uses a clear verb ('Get') and a specific resource ('the Privacy & Cookie Policy document for a site'), which is readily distinguishable from many siblings. It does not explicitly name alternatives such as get_pcp_service or get_terms_conditions, but the resource and site scoping are specific enough.

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?

No guidance is provided about when to choose this tool over closely related siblings such as get_pcp_service or get_site_pcp_service, and no exclusions or prerequisites are mentioned. The only contextual cue is 'for a site', which is already implied by the site_id parameter.

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