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

No annotations are supplied, so the description carries the burden of disclosure. It adds useful cost information and indicates the response includes current ratings, but it does not state read-only behavior, error handling, or auth/rate-limit constraints; for a simple lookup this is adequate but thin.

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 front-loaded sentence plus a cost note, with no filler. It could be slightly more structured, but every element earns its place.

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 one-parameter lookup, the description covers the resource, identifier, main return content, and cost. It leaves out how to obtain a location id and how this differs from cqc_search, so it is adequate rather than complete.

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 single locationId parameter is fully covered by the schema, so the baseline is 3. The description reinforces that the parameter is a CQC location id but adds no format, validation, or example beyond the schema.

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 names a specific resource (CQC location), scope (by location id), and return content (details and current ratings). It is clear enough to distinguish a by-id lookup from a generic search, though it does not explicitly name cqc_search as the alternative.

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 or when-not-to-use guidance. 'By location id' implies a direct lookup when an ID is known, but it does not tell the agent to use cqc_search first or explain prerequisites.

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