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

With no annotations provided, the description fully carries the burden. It discloses the official GOV.UK source, refresh cadence, row granularity, organisation-level scope, filter combination semantics, full-text q behavior, and credit cost per call.

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 dense and front-loaded: identity, scope, fields, granularity, source, refresh behaviour, and filtering rules are each conveyed in one short sentence or clause. There is no filler or repetition.

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?

The description is rich enough to invoke the tool correctly, covering data provenance, fields, row semantics, filtering, and cost. Pagination is left to the schema defaults. The only real gap is the lack of explicit allowed values for rating and sponsor_type, which creates minor uncertainty for a 9-parameter tool with no enum definitions.

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 compensates by mapping the data fields to the likely filter parameters and defining q as a full-text search. It also gives route examples. However, it does not enumerate accepted values for rating or sponsor_type, which remain ambiguous from the parameter names alone.

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 opens with a precise verb and resource: 'Every organisation on the Home Office register of licensed sponsors'. It names the exact data source, lists the returned fields, and specifies row granularity, making it clearly distinct from sibling query_uk_* tools.

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?

The description gives clear operational context: filters combine with AND, q searches all text fields, and the data is organisation-level only. It does not explicitly contrast with sibling tools, but the register is unique enough that no alternative could be confused with it.

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