site

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

With no annotations provided, the description carries the full burden, and it delivers: it states what the tool returns, clarifies that nothing is bought, ordered, or paid, that no quote is guaranteed, that it is free, and that the response includes recipient details, consent wording, and confirmation behavior. This is highly 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 front-loaded with the most important instruction ('Read first'). Every sentence adds distinct value: what the tool does, the key caveats, and what the returned content covers. No wasted words.

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 zero parameters, no annotations, and no output schema, the description fully explains the tool's purpose, return content, and semantic boundaries. Nothing critical is missing for an agent to decide whether and when to call 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?

The tool has zero parameters, so there are no parameter semantics to document. The schema coverage is 100% and the description needs no parameter details; the baseline of 4 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 specific verb ('states plainly') and resource ('what submit_enquiry does'), and clearly distinguishes this tool from the sibling submit_enquiry tool. It also explains the core semantic distinction: an enquiry with human providers, 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 context cue: this tool should be used before submitting an enquiry. It does not explicitly name the alternative tools or say when not to use it, but the context is clear enough for an agent to know this is preliminary/descriptive rather than an action tool.

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 but is mostly a structural description of the output. It does convey that this is a read-only metadata tool and implies no side effects, but it does not mention whether the field values or options are localized, whether the schema corresponds to a specific step, or what happens for conditional fields.

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, no filler. The first sentence is front-loaded with what the tool returns; the second sentence gives actionable guidance on using the result. 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 zero-input metadata tool, the description is nearly complete: it explains what is returned and how to use it. It is slightly short on guidance for choosing this versus enquiry_describe, but the field-level detail in the description largely makes the tool self-sufficient.

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 parameter semantics are inherently simple. The description correctly avoids inventing parameters and makes clear that the answer to how to use it is through the returned field keys, which is meaningful context.

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 names the tool as returning every field of a specific enquiry, enumerating what is included: key, label, type, required flag, help text, and allowed options. It distinguishes itself from siblings by being the field-schema/metadata tool for a Conveyancing Fees Ireland enquiry.

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 explicitly says to pass answers to submit_enquiry keyed by field key, which tells the agent how to use the output. It does not explicitly state the alternative is enquiry_describe or when to use that instead, so it lacks direct when-not-to-use 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, the description carries the full burden and does so: it discloses that step 1 only validates and returns a summary/consent line/confirmation token, that step 2 actually submits, that a confirmation email link must be clicked before any provider sees the data, and that details go to at most three solicitors the person can stop. This is far more behavioral context than the schema provides.

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 and dense, with the disclaimers and step ordering before any details. It loses a point only because the consent text is quoted in full and is already duplicated verbatim in the schema's consent description, which is a redundancy rather than an earned sentence.

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 and no annotations, so the description must explain return values itself, and it does: step 1 returns a summary, consent line and confirmation token, and step 2 triggers an email with a click-through link. For a stateful two-call tool with a nested object parameter, this is complete enough to drive the flow 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 coverage is already 100%, so the baseline is 3, but the description adds real cross-parameter meaning the schema cannot: 'answers' must be keyed by field key from enquiry_fields, and 'confirmation' is specifically the token returned by step 1 and must accompany the same answers. That dependency chain is the most valuable thing a caller needs and it is only in the prose.

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?

Starts with a specific verb and resource ('Submits an enquiry to Conveyancing Fees Ireland') and immediately rules out the two most likely misreadings ('NOT a purchase, NOT a guaranteed quote'). It also ties itself to the sibling tool by stating answers are 'keyed by field key from enquiry_fields', so an agent can place it in the tool family without opening a 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?

Gives an explicit two-step protocol with the condition that gates step 2 ('only if the person agrees') and states exactly what to do with step 1's output ('show the person the summary and the consent line'). No alternatives-based routing is offered, but none is needed because this is the terminal action of the flow and the description makes the ordering unambiguous.

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