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

With no annotations, the description carries the full burden and does substantial work: it discloses that nothing is bought, ordered, or paid, that no quote is guaranteed, that it is free, and that it returns who receives details, the consent wording, and confirmation method. It could be even more explicit about having no side effects, but the explanatory framing makes that reasonably clear.

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 front-loaded with 'Read first' and the core purpose, then adds only high-value clarifications in compact sentences. Every sentence earns its place and there is no meaningful 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 tool with no output schema, the description is complete: it states the tool's role, what it returns, and the important user-facing caveats. The sibling relationship is handled by naming submit_enquiry and using 'Read first' to signal the correct ordering.

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?

There are zero parameters and schema coverage is 100%, so the baseline is 4. No parameter-specific explanation is needed because there are no parameters to explain.

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 explicitly names the verb 'States plainly' and the resource 'submit_enquiry on Commercial Drainage Quotes', so an agent can tell this is an explanatory tool rather than the submission action itself. It also differentiates from the sibling submit_enquiry by framing itself as the 'Read first' companion.

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 leading 'Read first' is clear usage guidance: consult this tool before submit_enquiry. It does not explicitly address enquiry_fields as an alternative, but for a zero-parameter informational tool the placement and content give sufficient context.

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