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

With no annotations, the description carries the full burden and does so thoroughly: it discloses validation on step 1, the returned summary/consent line/token, the human-approval gate, the double-send semantics of step 2, and the downstream side effect that the person must click an emailed link before any provider sees the data. Consent scope (up to three bureaus, chosen by Payroll Dates, contactable directly) is spelled out.

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 purpose and the not-a-purchase guard, then cleanly structured into Step 1 / Step 2. It is dense but each clause carries load; the only mild redundancy is the consent text quoted verbatim in the schema, which is defensible given the legal nature of consent.

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?

There is no output schema, yet the description explains what step 1 returns (summary, consent line, confirmation token) and what step 2 triggers (submission plus a verification email). Prerequisites, state requirements, and side effects are all covered, leaving nothing an agent needs to call this correctly.

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 the baseline is 3, but the description adds workflow meaning the schema does not: 'answers' must be keyed by field keys from enquiry_fields, 'consent' must be true, and 'confirmation' is the token from step 1 that is only supplied on the second call. That clarifies the role each parameter plays across the two-step flow.

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 and resource ('Submits an enquiry to Payroll Dates') and immediately bounds it with what it is not ('NOT a purchase, NOT a guaranteed quote'). The title reinforces that it is a two-step submission rather than an instant purchase, which clearly separates it from siblings like calculate or enquiry_fields.

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?

Explicitly prescribes when to call step 1 (with answers and consent=true) and when to call step 2 ('only if the person agrees'), including the required state (same answers plus the confirmation token). It also points to enquiry_fields as the source of field keys, routing the agent to the correct supporting tool.

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