site

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

With no annotations, the description takes on the transparency burden. It discloses key behavioral facts about the described flow: nothing is bought/ordered/paid, no quote is guaranteed, and it is free. It also states what the tool returns, including who receives the details, consent wording, and confirmation method. It does not explicitly state that this tool itself is side-effect-free, but 'Read first' and 'States plainly' strongly imply a read-only explanation.

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 extremely efficient: a front-loaded 'Read first' followed by one dense sentence that covers purpose, scope, constraints, and output. There is no redundancy or filler.

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 explainer tool, the description is nearly complete: it names the flow it explains, states key constraints, and lists what is returned. It could add an explicit mention that this is the correct tool to understand submit_enquiry before calling it and how it relates to enquiry_fields, but the core context is present.

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. There are no parameter semantics for the description to add; the empty schema plus the tool's explanatory purpose are sufficient.

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: 'States plainly what submit_enquiry does on NEBOSH Course Cost'. It clearly marks this as an explanatory tool rather than the submission action itself, which differentiates it from submit_enquiry. It does not explicitly differentiate from the sibling enquiry_fields, and the title's 'What you get: an ENQUIRY' could be momentarily misleading, so it stops short of a 5.

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 instruction 'Read first' gives an explicit usage cue that this tool should be called before the submission flow. The description also gives enough context about what submit_enquiry does so an agent can decide this is informational. It does not name enquiry_fields or give when-not-to-use conditions, so it lacks full alternative 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 burden of behavioral disclosure. It specifies what data will be returned and notes that allowed options may exist. However, it does not explicitly state that this is a read-only introspection call, nor does it describe any side effects, error conditions, or output formatting beyond the listed field attributes.

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, immediately naming what the tool covers and enumerating the useful attributes. Every sentence contributes: the first describes the payload, and the second ties it to the related submission tool. No filler or 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 metadata lookup tool, the description covers the key information an agent needs: what fields exist, what each entry contains, and how to use the results with submit_enquiry. The main gap is the lack of explicit differentiation from enquiry_describe, which could leave an agent unsure which sibling to call for a broader description of the enquiry.

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 empty input schema is complete. The description still adds value by explaining how the returned field keys should be used with submit_enquiry, which is the relevant semantic context even though there are no parameters 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 provides every field of the NEBOSH Course Cost enquiry, including key, label, type, required flag, help text, and allowed options. It is clear about the resource and the kind of data returned, but it does not explicitly contrast itself with the sibling enquiry_describe tool.

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 direct usage hint: pass answers to submit_enquiry keyed by field key, which connects this introspection tool to the submission workflow. It does not explicitly describe when to prefer enquiry_describe over enquiry_fields, but the context of building submission payloads is reasonably 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 are provided, so the description carries the full burden and does so: it discloses that step 1 validates and returns a summary/consent line/token, that the enquiry is only submitted on the second call, that the person must click an emailed link before any provider sees the data, and it spells out the exact consent text. This is unusually rich disclosure for a mutation 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?

Front-loaded with the key distinction (not a purchase) and then sequenced in call order, so every sentence does work. It is on the long side because it embeds the full verbatim consent text, which is justified but makes the block dense; a slight trim of the embedded quote would help readability without losing information.

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 two-call write tool with no output schema, the description covers the whole lifecycle: validation, what is returned at each step, the consent gate, the email-confirmation step, and the downstream disclosure to up to three providers. Nothing an agent needs in order to call it correctly at either step 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 real semantics beyond the schema: 'answers' is keyed by the field key from enquiry_fields, 'consent' must be true only after the person agreed to the quoted text, and 'confirmation' is the token returned by step 1 and only used after the person approves the summary. The flow-level meaning of each parameter is not derivable from the schema alone.

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 NEBOSH Course Cost') and immediately negates the two most likely misreadings ('NOT a purchase, NOT a guaranteed quote'). An agent can distinguish it from enquiry_describe/enquiry_fields, which are clearly read-side discovery 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?

Gives an explicit two-step protocol with the exact conditions for each call: step 1 with answers + consent=true, step 2 only if the person agrees, with the same answers plus the confirmation token. When-not-to-proceed is stated ('only if the person agrees') and the human-approval gate is unambiguous.

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