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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the bar is lower. The description still adds real value beyond them: cost ('FREE'), the disclosure of a privacy notice and version, the named human contact, and the limits of what it guarantees (no capacity promise, not an emergency service).

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?

Two tightly packed sentences with no filler, and the most decision-relevant token ('FREE') is front-loaded. The phrasing is telegraphic in places ('privacy notice/version', 'current enquiry capability'), which slightly costs readability but not length.

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 zero-parameter, read-only, closed-world lookup with no output schema, the description covers what comes back and what is disclaimed, which is close to everything an agent needs. The main remaining gap is not connecting this option lookup to the sibling submission flow it presumably precedes.

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 tool takes zero parameters, so the schema requires no semantic elaboration and the baseline is 4. The description does not add anything about invocation that a zero-parameter call needs, and instead spends its words on return content, so it lands at the baseline rather than above 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 description states a specific verb and enumerates what is returned: services, exact coverage, recipient, privacy notice/version, and current enquiry capability for the named provider L&G. This makes the tool's function distinguishable from the sibling submit_direct_installation_inquiry, though the description never names that sibling or explicitly frames itself as the read-only pre-check.

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?

Usage context is implied ('FREE', 'current enquiry capability') and one exclusion is stated: 'no capacity promise or emergency service', which tells the agent not to rely on it for urgent or guaranteed-capacity reasoning. However, there is no explicit when-to-use statement and no routing to the sibling tools such as submit_direct_installation_inquiry or find_service_providers.

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