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

With no annotations, the description carries the full burden, and it does disclose pagination behavior ('50 a page'). However, it says nothing about result ordering, how to page beyond the first set, total counts, or authentication/permission requirements, leaving meaningful gaps.

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?

A single dense sentence with no wasted words, front-loading the resource and region scope before the optional filter and page size.

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 4-parameter tool with 0% schema coverage and no annotations or output schema, the description covers region and service but leaves page/pageSize semantics and return shape unexplained. Adequate but with clear gaps.

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. It adds real meaning for 'region' (a state or jurisdiction, accepted by id or name) and clarifies 'service' is optional, but says nothing about page/pageSize beyond the ambiguous '50 a page' hint.

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 concrete resource and scope: entities in one region of the Roofing Quotes UK register, with an optional service filter. The garbled phrasing ('The Roofing Quotes UK register entities in one region') lacks a clean verb, but the region-scoping distinguishes it from siblings like entities_search and entities_export.

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 when-to-use or when-not-to-use guidance is given, and no alternatives are named. The agent must infer that this tool is for enumerating all entities in a region, with no hint about how it relates to entities_search or entities_export.

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