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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description earns credit for adding behavioural context beyond that: the exact return shape (Markdown plus author, reviewer, last-verified date, official sources), which matters since there is no 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 sentences, zero filler, and front-loaded with the payoff (returned format and provenance) before the accepted inputs. Nothing redundant with the name or title.

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 single-parameter read tool with no output schema, the description supplies the return content that would otherwise be missing and enumerates valid input forms. It omits failure behaviour (invalid id, unreachable URL), which is a minor gap given the rich annotations.

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 single parameter's description already enumerates the accepted forms, including the programme/<...> enum-like section list. The description restates these forms in prose without adding format, validation, or error semantics, so the baseline 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 states a specific verb and resource ('Returns one document as Markdown') and lists the return payload (provenance, sources), so the agent knows exactly what comes back. It stops short of distinguishing itself from near-neighbours like get_mprp_programme or list_content, both of which could plausibly return document-like content.

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?

Usage is implied rather than stated: accepting 'a search result id' hints that this follows a search call, and the accepted input forms are enumerated. However, there is no explicit when-to-use guidance, no exclusions, and no routing against the sibling tools that also serve programme/property content.

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