site

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states nothing is bought, ordered, or paid, no quote is guaranteed, it is free, and it lists the return content (who receives details, consent wording, confirmation). This is strong transparency for an informational tool.

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 packs necessary information without wasted words, though the semicolon-dense middle sentence is slightly less readable than ideal.

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?

Given no output schema and zero parameters, the description covers the return content, its relationship to submit_enquiry, and safety expectations (no purchase). Nothing an agent needs to call this tool correctly is missing, though a brief note on enquiry_fields would enhance completeness.

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?

There are zero parameters and schema coverage is 100%, so the description has nothing to add about inputs. The baseline of 4 for a no-parameter tool applies.

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 clear, specific purpose: to explain what submit_enquiry does on Marine Survey Cost. It distinguishes itself from the sibling submit_enquiry by being a read-first informational tool, and the title reinforces that it is about an enquiry, 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' is an explicit when-to-use directive, positioning this tool before submit_enquiry. It clarifies what the tool is not (a purchase or guaranteed quote), but it does not explicitly contrast with enquiry_fields, so it stops short of a 5.

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 behavioral burden. It discloses the nature of the tool as a read-only enumeration of enquiry fields and details what the agent will receive. It does not mention response format or authentication, but for a zero-parameter introspection tool this is adequately 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?

Two sentences with no filler. The first fronts the resource and its content, and the second immediately connects the output to the next actionable step. Every sentence 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 simple zero-parameter, no-output-schema tool, the description is complete enough to call correctly: it states what is returned and how to use the returned keys. The only minor gap is the lack of any distinction from enquiry_describe, but this does not block correct invocation.

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 input schema carries no burden. The description adds meaningful semantic context by specifying that the returned 'key' is the value to use when submitting answers to submit_enquiry.

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 identifies the resource ('every field of the Marine Survey Cost enquiry') and enumerates the exact content: key, label, type, required flag, help text, and allowed options. It also distinguishes itself from submit_enquiry by noting that answers should be keyed by field key, though the verb is implicit rather than explicit.

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?

It gives a clear workflow instruction: obtain the fields first, then pass answers to submit_enquiry keyed by field key. However, it does not explain when to prefer this tool over the sibling enquiry_describe, leaving that distinction to inference.

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 full behavioral burden and succeeds admirably. It discloses validation, the returned summary and consent line, the email notification, the requirement that the person click the emailed link before providers see the enquiry, and exact consent wording.

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 dense but appropriately so for a two-step stateful operation. It front-loads the key disclaimer and then structures step 1 and step 2 clearly. Slightly long, but every clause contributes necessary behavioral context.

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, so the description must explain return values and side effects. It does: step 1 returns a summary, consent line, and confirmation token; step 2 triggers the email and eventual provider visibility. It also references enquiry_fields for constructing answers, making the tool self-contained.

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 meaningful guidance by tying answers to field keys from enquiry_fields and clarifying the confirmation token's role. The consent text in the schema is enriched by explaining it represents the person's agreement before submission.

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 opens with a specific verb and resource: 'Submits an enquiry to Marine Survey Cost.' It immediately disambiguates what the tool is not ('NOT a purchase, NOT a guaranteed quote'), which clearly separates it from any transaction-like sibling and conveys the core intent.

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 spells out a two-step protocol with explicit conditions: step 1 requires answers and consent=true, then step 2 is gated on the person agreeing and on supplying the confirmation token. This tells an agent exactly when to call and what each invocation accomplishes.

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