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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it succeeds. It reveals that the tool is stateful (requires a confirmation token from step 1), that submission triggers an email with a click link, that providers see the enquiry only after that click, and that consent has a specific definition. Side effects and consent implications are clearly disclosed.

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 appropriately sized for a two-step, high-stakes submission tool, and it front-loads the most important caveat ('NOT a purchase, NOT a guaranteed quote'). The workflow is logically ordered into Step 1 and Step 2, and every sentence carries necessary operational or consent-related information without padding.

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 the tool's complexity and the absence of an output schema, the description provides complete operational context: prerequisites, return values of step 1, conditions for proceeding to step 2, and the post-submission outcome. An agent can correctly execute both steps and understand expected behavior without additional information.

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 schema already documents all three parameters at 100% coverage, so the baseline is 3. The description adds meaningful workflow semantics: answers are keys from enquiry_fields, consent must reflect the quoted agreement, and confirmation is the step-1 token used in the second call. This goes beyond the schema by explaining how the parameters interact across the two-step flow.

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 Fax Line Index.' It explicitly disambiguates the action as 'NOT a purchase, NOT a guaranteed quote' and clearly separates the tool from the dataset_* siblings and the enquiry_describe/enquiry_fields tools. The two-step workflow reinforces exactly what operation this tool performs.

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 when-to-use instructions: call first with answers and consent=true, show the summary to the person, and only call again if the person agrees, passing the confirmation token. It also tells the agent where answers come from ('keyed by field key from enquiry_fields'), connecting this tool to a sibling prerequisite. The 'NOT a purchase' statement helps the agent avoid selecting this tool for purchase-like actions.

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