site

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

No annotations are present, so the description carries the burden of explaining behavior. It clearly indicates this tool 'states' and 'returns' information, implying a read-only, side-effect-free operation, and it adds useful context about what submit_enquiry does (free, no purchase, no guaranteed quote). It stops short of an explicit 'this tool does not actually submit', but the framing is strong and unambiguous.

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 three tight sentences with no filler, and the most important directive ('Read first') is front-loaded. Every sentence earns its place by either explaining the tool's function, clarifying what it is not, or listing what it returns.

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?

This is a zero-parameter, no-output-schema informational tool, and the description names the concrete outputs you can expect: who receives the details, the consent wording, and how the person confirms. That is sufficient for an agent to decide whether to call this before submit_enquiry and to know what it will get back.

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 input schema has zero properties, and the description correctly adds no parameter documentation because none exists. With 0 parameters, the baseline of 4 applies and the description fully satisfies this dimension.

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 uses a specific verb ('states plainly') and names the exact resource it describes ('submit_enquiry'), so an agent knows this is a reference/explanation tool rather than the submission tool itself. The title also frames it as a non-action output ('not a purchase, not a guaranteed quote'), clearly distinguishing it from its 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?

'Read first' is an explicit usage directive telling the agent to invoke this before acting, and the description frames itself as a pre-submission reference for submit_enquiry. It does not explicitly discuss when to use enquiry_fields instead, but the core choice between describing and submitting 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?

With no annotations, the description carries the burden of behavioral disclosure. It transparently states what the tool returns: all fields with their metadata and allowed options. It does not explicitly describe side effects, but a field-listing tool is clearly non-mutating and the description communicates its scope accurately.

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 and every word earns its place. The first sentence compactly enumerates the field attributes, and the second sentence links the output to the related submit_enquiry tool with direct usage guidance.

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 low-complexity, zero-parameter tool with no output schema, the description is reasonably complete: it specifies the exact content scope and how to use the result. It could be slightly stronger by clarifying how this tool relates to enquiry_describe, but the provided context is sufficient for 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 input schema is empty with 0 parameters, so there are no parameter semantics to explain. The baseline for zero-parameter tools is 4, and the description appropriately adds no unnecessary parameter information.

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 provides every field of the Private Surgery Costs enquiry along with key attributes such as label, type, required flag, help text, and allowed options. It distinguishes itself from submit_enquiry by mentioning that answers are passed to submit_enquiry keyed by field key, though it does not explicitly contrast with 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 actionable usage guidance by telling the agent that answers should be passed to submit_enquiry keyed by field key, implying this tool is the source for valid keys. It does not explicitly state when to use this tool versus enquiry_describe, but the guidance is clear enough for the primary intended workflow.

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 succeeds. It discloses the validation step, the confirmation token flow, the email with a click-link requirement, and the exact consent wording. No behavioral surprises are left for the agent to discover.

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 detailed but every sentence earns its place by explaining a required step, condition, or side effect. The structure is logical: purpose, step 1, step 2, and the consent meaning. It is long only because the workflow genuinely requires it.

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 tool with no annotations and no output schema, this description is remarkably complete. It covers the two-step protocol, the intermediate token, the consent condition, the email link requirement, and what happens before providers see the enquiry. The agent has enough context to handle a complex human-interaction flow.

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?

Although the schema already describes all three parameters, the description adds crucial context: answers are keyed by field key from enquiry_fields, consent must match the quoted agreement, and confirmation is the token produced in step 1. This materially improves the agent's ability to invoke the tool correctly.

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 a specific action — submitting an enquiry to Private Surgery Costs — and explicitly distinguishes it from a purchase or guaranteed quote. It also conveys the two-step nature, which separates it from typical one-shot submission tools.

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 explicit step-by-step usage instructions: call once to validate and get a token, then call again with consent and token only after the person agrees. It does not explicitly compare with the sibling tools, but the workflow guidance is strong enough for correct invocation.

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