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

There are no annotations, so the description carries the burden. It clearly says the tool evaluates readiness and reports blocking gaps, which is useful behavioral information. It does not explain decision semantics, fail-closed treatment of nullable evidence fields, or whether the tool is purely computational, leaving some behavioral ambiguity.

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 sentence with no filler. It front-loads the core purpose and then enumerates the concrete gap categories, so every part of the description 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 complex payload with no output schema, the description states the goal and gap categories while the nested schema supplies field-level details. Missing are the expected output statuses (e.g., READY/REVIEW) and how unverified nullable evidence affects the decision, so completeness is adequate but not thorough.

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 parameter-level schema coverage is 0%, but the description meaningfully maps to payload fields by naming 'premises, staff, DBS, role, and supporting-document gaps'. It does not explain key payload inputs such as service_type or legal_entity_type, though their schema titles make them reasonably self-evident.

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 uses a specific action ('Check') and a specific target ('CQC new-provider application readiness'), then lists the kinds of gaps it identifies. This clearly differentiates it from sibling preflight tools that focus on narrower concerns such as location, structure, or required documents.

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 purpose implies when it should be used: when assessing a CQC new-provider application. However, it gives no explicit when-not-to-use guidance or references to alternative readiness-related siblings such as cqc_provider_structure_preflight or cqc_required_documents, so the agent must infer the appropriate call boundary.

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