site

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

With no annotations provided, the description carries the full burden. It explains that the tool describes an enquiry flow, clarifies that nothing is bought, ordered, or paid, and states what information is returned: recipient of details, consent wording, and confirmation method. This gives a solid behavioral picture for a read-only informational tool, though it never explicitly says 'this tool itself makes no changes.'

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?

Three sentences, each earning its place. The 'Read first' directive is front-loaded, the main purpose is stated plainly, and the boundary conditions (no purchase, no guarantee, free) plus return-content summary are packed into a compact description with no redundancy.

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 without an output schema, the description fully covers what the tool does, what it returns, and how to approach it. It also references the related submit_enquiry tool to orient the agent. Nothing essential 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?

The tool has zero parameters and 100% schema description coverage, so the baseline is 4. The description adds no parameter-specific semantics, which is appropriate since there are no parameters to explain.

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 resource: it 'states plainly what submit_enquiry does on Void Clearance Quotes.' It clearly distinguishes itself from submit_enquiry by being the explanatory/pre-flight tool rather than the action tool, and the title reinforces that it describes an enquiry experience, not a purchase or guaranteed quote.

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 opening 'Read first' gives an explicit placement in the workflow, indicating this tool should be consulted before using submit_enquiry. It also clarifies what the user will not get (no purchase, no paid order, no guaranteed quote, free), which sets expectations. It does not explicitly contrast with enquiry_fields, but the 'Read first' instruction and naming of submit_enquiry provide adequate guidance.

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 provided, the description carries the burden of explaining behavior. It clearly states what information is returned, but does not explicitly say this is a read-only retrieval operation, nor does it discuss error conditions or authentication. For a metadata lookup tool, the stated content is reasonably transparent.

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 information-dense. The first sentence enumerates exactly what fields are returned, and the second sentence gives the actionable relationship to submit_enquiry. Every word earns its place, and the description is front-loaded with the core purpose.

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 metadata tool with no output schema, the description fully specifies the output contents and connects them to the downstream tool. There are no significant gaps: the agent knows what data will come back, how it is structured conceptually, and how to use it.

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?

This tool has zero parameters, so the schema is already fully covered. The description adds useful semantic context beyond the schema by explaining that the returned field keys should be used as keys when calling submit_enquiry, which helps an agent connect the output to a subsequent invocation.

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 what the tool provides: every field of the Void Clearance Quotes enquiry with its key, label, type, required status, help text, and allowed options. It identifies the exact resource and content scope, though it does not explicitly contrast itself with the sibling 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 practical usage guidance by telling the agent to pass answers to submit_enquiry keyed by field key, showing how this tool feeds into submission. It does not explicitly mention when not to use it or compare against enquiry_describe, but the intended workflow is clear.

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?

No annotations exist, so the description carries the full behavioral burden and does so richly: it discloses that step 1 validates and returns a summary/consent line/token, that submission triggers an email requiring a click before any provider sees the data, and the exact data-sharing scope (up to three contractors, emailed each firm's name, can stop further sharing).

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 two-step flow before the quoted consent text, and most sentences are load-bearing. The consent wording is unavoidably long and is also duplicated in the schema's consent description, a minor redundancy.

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?

With no output schema, the description correctly explains what step 1 returns (summary, consent line, confirmation token) and what the human sees afterwards (email with a required click). An agent has everything needed to drive the flow correctly, including the approval gate.

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 procedural meaning beyond the schema: 'answers' is keyed by field key from enquiry_fields, and 'confirmation' is the step-1 token used only in the second call. It does not add format/syntax detail beyond that.

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 Void Clearance Quotes') and immediately distinguishes it from what it is not ('NOT a purchase, NOT a guaranteed quote'). Since siblings are enquiry_describe and enquiry_fields, this clearly marks itself as the mutating submit action versus the read-only helpers.

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 an explicit two-step protocol with the exact conditions that select each call: Step 1 with answers + consent=true, Step 2 'only if the person agrees' with the confirmation token. The dependency on enquiry_fields for field keys is also stated.

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