site

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

With no annotations, the description carries the burden and does well: it discloses that nothing is bought, ordered, or paid for, that no quote is guaranteed, and that the tool returns who receives details, consent wording, and confirmation method. The read-only nature is implied by 'Read first' and 'States plainly'.

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 compact and front-loaded with 'Read first.' It conveys the purpose, key behavioral caveats, and return content in three sentences without significant waste, though the title is somewhat wordy.

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 informational tool with no output schema, the description is sufficiently complete: it tells the agent what the tool explains, what is not involved, and what will be returned. No critical invocation details are 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?

The tool has zero parameters, so the baseline of 4 applies. The description appropriately focuses on what the tool returns rather than parameter usage, since no parameters exist to document.

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 clearly states that this tool is a read-first explanation of what submit_enquiry does: it starts an enquiry with human providers, not a purchase or guaranteed quote. This distinguishes it from the sibling submit_enquiry action and gives the agent a clear reason to call it.

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?

'Read first' explicitly tells the agent to use this before acting on submit_enquiry. It does not explicitly contrast with enquiry_fields, but the context that this explains submit_enquiry's behavior is clear enough for routing.

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

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

With no annotations, the description carries the full burden of explaining behavior. It discloses exactly what the tool returns: the fields' keys, labels, types, required flags, help text, and allowed options. The wording suggests a read-only metadata lookup, and directing answers to submit_enquiry reinforces that this tool itself does not submit. It does not mention side effects, but none are implied.

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 two sentences with no filler. The first sentence front-loads what the tool provides, and the second gives a concise, actionable usage note. Every word 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 zero-parameter, no-output-schema metadata tool, the description is nearly complete: it names the resource, the fields returned, and how to use the results. The only missing piece is a direct comparison with enquiry_describe to fully disambiguate from a sibling tool, but overall it gives an agent enough to call it 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?

The tool has zero parameters and the schema is empty, so there is nothing to document. The description adds useful context about the returned values' structure and how they map to submit_enquiry, which helps the agent use the output correctly. The baseline for zero parameters is 4, and the description meets 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 clearly states that the tool exposes the field definitions of the Subsidence Survey Cost enquiry, listing key, label, type, required status, help text, and allowed options. This is a specific resource with a clear purpose. It implicitly differentiates from submit_enquiry by directing answers to that tool, but does not explicitly distinguish from enquiry_describe.

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 a useful downstream instruction: 'Pass answers to submit_enquiry keyed by field key.' This implies the tool is used to discover the fields needed for submission, but it does not explicitly state when to choose this tool over enquiry_describe or when not to use it. The usage context is clear but not fully elaborated.

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

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: it discloses validation behavior, the returned summary/consent line/token, the email confirmation link that must be clicked before providers see the enquiry, the distribution to up to three structural engineers, and the ability to stop further sharing. Authentication/safety profile is not applicable here, but the flow-dependent side effects are fully 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 not-a-purchase disclaimer and the two steps, and every clause earns its place except the consent text, which is quoted verbatim again despite already being in the schema's consent property description. Slightly redundant but defensible for legal accuracy.

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 and no annotations, yet the description explains what each call returns (summary, consent line, confirmation token) and the downstream effect (email link required before provider visibility). For a multi-step, nested-object, side-effecting tool, nothing an agent needs to invoke it 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 the baseline is 3, but the description adds genuine meaning: it explains that answers must be keyed by field key from enquiry_fields, that consent must be true, and that confirmation is the token returned by Step 1 used only after the person approves the summary. That exceeds what the schema alone conveys.

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 Subsidence Survey Cost') and immediately disambiguates intent with 'NOT a purchase, NOT a guaranteed quote'. It also routes to the sibling tool by specifying answers keyed by field key from enquiry_fields, so the agent can distinguish it from enquiry_fields/enquiry_describe without opening schemas.

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-use instructions for both steps: Step 1 always with answers and consent=true, Step 2 only if the person agrees and with the confirmation token. It also frames what the tool is not (no purchase, no guaranteed quote), removing the main risk of misuse.

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