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

No annotations are provided, so the description carries the full behavioral burden, and it does substantial work: it discloses that step 1 only validates and returns a summary/consent line/token, that submission happens on step 2, and that the person must click an emailed link before any provider sees the enquiry. It does not describe failure/validation-error behavior or what happens if the token is stale, but the core side-effect chain is well covered.

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?

Front-loaded with the critical disambiguation, then the two-step flow in order, then the consent text. It is long, and the consent wording is duplicated verbatim from the schema's consent description, but for a legally significant consent the repetition is defensible and every sentence carries information.

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?

No output schema exists, and the description compensates by stating exactly what step 1 returns (summary, consent line, confirmation token) and what the person receives after step 2 (an email link they must click). Nothing an agent needs to drive the two-call flow correctly is missing.

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 coverage is 100%, so baseline is 3, but the description adds sequencing meaning the schema cannot: 'answers' are keyed by field key from enquiry_fields, 'consent' must be true only after the person has read and agreed, and 'confirmation' is the token returned by step 1. That context makes the otherwise flat parameters actionable.

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?

States a specific verb (submits) and resource (an enquiry to HMO Licence Checker), and immediately disambiguates by negating the two things an agent might confuse it with ('NOT a purchase, NOT a guaranteed quote'). The two-step framing further distinguishes it from the checker_* and enquiry_* siblings.

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?

Gives explicit when-to-call instructions for both steps: step 1 with answers and consent=true, step 2 only if the person agrees, with the same answers plus the confirmation token. It also names the prerequisite source for the answers (field keys from enquiry_fields).

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