site

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

With no annotations the description carries the full burden, and it does disclose meaningful behavioral traits of the downstream action: nothing is bought, ordered or paid, no quote is guaranteed, and it is free. It also names the returned content (recipients, consent wording, confirmation). It does not explicitly restate that this describe call itself is a read-only, side-effect-free operation.

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 'Read first,' followed by two compact sentences; every sentence carries information about either the purpose or the guarantees, with no 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 describe tool with no output schema and no annotations, the description covers what the call is for and roughly what it returns, which is enough for an agent to invoke it. It could be slightly stronger by naming enquiry_fields as the field-level alternative.

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?

Zero parameters, so the baseline is 4; there is nothing for the description to disambiguate and it correctly omits parameter discussion.

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 concrete purpose: it plainly explains what submit_enquiry does, and it enumerates the specific returns (who receives details, consent wording, how the person confirms). It clearly marks the boundary against the action sibling submit_enquiry ('not a purchase, not a guaranteed quote'), though it never distinguishes itself from enquiry_fields.

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' gives an implied ordering cue (call this before submit_enquiry), but there is no explicit when-to-use/when-not statement and neither sibling alternative (enquiry_fields) is named or routed to.

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 and no output schema, the description carries the burden and does disclose the returned payload in detail. Read-only/non-mutating nature is strongly implied by the listing content but never stated, and no auth or caching behavior is mentioned.

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, front-loaded with what is returned and followed by the one actionable instruction. No 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 reader, the description covers the return shape and the follow-up step adequately. It lacks any statement of read-only behavior or sibling routing, which would fully close the gap.

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 takes zero parameters, so per the rubric the baseline is 4. The mention of 'keyed by field key' adds useful semantics about how returned keys map into 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 states a specific resource and enumerates its contents (key, label, type, required, help text, options), so an agent knows this returns the enquiry form's field metadata. It does not explicitly differentiate itself from the sibling enquiry_describe, which likely also describes the enquiry, so it falls short of the 5 bar.

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 final sentence gives clear downstream context: answers go to submit_enquiry keyed by field key, which implies this should be read before submitting. It does not address when to prefer this over enquiry_describe, so no exclusions are provided.

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 mostly meets it: it discloses that step 1 is validation-only, what step 1 returns (summary, consent line, token), that step 2 triggers an email with a click-through gate before any provider sees the enquiry, and the exact wording consent covers. It is silent on failure modes (invalid field keys, expired or reused token, double submission), which matters for a two-step mutation.

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-loads the exclusions and then walks the two steps in order, with the consent definition quoted verbatim so the agent can reproduce it. It is dense but every clause carries operational weight; the quoted legal text and the restatement of 'the same answers, consent=true' in step 2 are the only slightly redundant portions.

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?

The tool has no annotations and no output schema, yet the description covers the full lifecycle: what step 1 returns, what the agent must show the user, the gating condition for step 2, and the post-submission email verification barrier. Given the complexity of a consent-gated two-call mutation, this is sufficient for an agent to execute 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?

Schema description coverage is 100%, so baseline is 3, but the description adds real meaning beyond the schema: 'answers' must be keyed by field keys sourced from enquiry_fields, consent must be a genuine affirmative, and 'confirmation' is the token returned by step 1 and only passed after the person approves the summary. That sequencing context 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?

Opens with a specific verb+resource ('Submits an enquiry') and immediately scopes it with two exclusions ('NOT a purchase, NOT a guaranteed quote') plus the audience ('SEO for B2B companies'). An agent can distinguish this from the sibling enquiry_fields/enquiry_describe tools, which only read field definitions, without opening any schema.

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 an explicit two-step protocol with the exact condition that selects each step ('Step 2: only if the person agrees...'). It also ties the answers to the sibling tool ('keyed by field key from enquiry_fields') and states the consent precondition, so there is no inference required about when to invoke or re-invoke.

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