UK CQC Care Ratings MCP

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

With no annotations, the description carries the full behavioral burden. It discloses a free preview, a hard cap of five results, and an outbound-related setting, but 'Soft-Offer outbound is OFF' is unexplained and it omits read-only/auth/error behavior.

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 short and front-loads the key constraints. The final phrase about Soft-Offer outbound is cryptic, but overall there is no filler and the structure is efficient.

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 two-parameter discovery tool with no annotations or output schema, it establishes the resource, geography, and result cap. It still leaves size semantics, exact return shape, and the unexplained outbound jargon unresolved.

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 50%, so the description needs to compensate for undocumented parameters. It clarifies that postcode is in England and implies a five-result cap, but it does not explicitly define the size parameter or its allowed values.

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 clearly states the resource and scope: CQC-regulated care locations for a postcode in England, with a maximum of five results. It is specific enough to understand the tool, but it does not explicitly differentiate itself from cqc_pack or redeem_pack.

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?

'Free peek, max 5' implies a limited preview use case, giving some when-to-use context. However, it never names the sibling tools or explains when to use cqc_pack/redeem_pack instead, so the choice is left to inference.

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

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

With no annotations, the description does carry useful behavioral context: it is paid, costs £0.49, returns a Stripe Checkout URL, and says Soft-Offer outbound is OFF. However, it does not explain whether invoking it charges immediately, what happens after checkout, or whether redemption is required via redeem_pack.

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 short and front-loads the key facts: paid pack, checkout URL, and domain scope. The final sentence is cryptic but may convey operational context, so the text is efficient though slightly fragmented.

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 paid tool with no output schema and undocumented parameters, the description is incomplete. It states the return artifact but omits the size parameter, checkout-to-redemption flow, and why an agent would choose this over cqc_discover or redeem_pack.

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 0%, so the description must compensate for both parameters. It only implies that postcode is relevant and gives no format details, and it entirely omits what the size parameter means or how it affects the result or price.

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 return artifact (Stripe Checkout URL) and the domain scope (CQC-regulated care locations for an English postcode). It also signals that this is a paid pack, which helps distinguish it from a free discovery sibling, though it does not explicitly name or contrast cqc_discover or redeem_pack.

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 guidance on when to use this tool versus cqc_discover or redeem_pack. The 'Paid pack' phrase implies a paid path, but the description does not state prerequisites, alternatives, or when-not-to-use conditions.

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

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

No annotations are provided, so the description carries the full disclosure burden. It says nothing about side effects (does it grant entitlements or credit a pack?), idempotency on repeated redemption, error behavior for unpaid/invalid sessions, or required auth, all of which are essential for an unreversible-sounding redemption 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?

It is short, but brevity here comes from under-specification rather than efficiency; a single fragmentary sentence that reads like a heading and conveys almost nothing front-loaded.

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 mutation-style tool with zero annotations, no output schema, and an undocumented required parameter, the description provides none of the context needed to invoke it correctly or interpret the result.

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 0% and the single required parameter session_id is completely undocumented in the description. The agent gets no indication that the identifier is a Stripe Checkout session ID, what format it takes, or how to obtain it.

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 text reads as a title fragment ('How to redeem...') rather than a statement of what the tool does. It gestures at the resource (a paid Stripe Checkout session) but never says the tool actually performs the redemption or returns anything, leaving the verb ambiguous.

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?

Mentioning 'paid' implies this only applies to completed checkout sessions, which is a faint usage cue. But there is no explicit when-to-use, no prerequisites, and no reference to the sibling tools epc_pack or epc_discover, which are plausible alternatives an agent would need to disambiguate against.

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