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

With no annotations provided, the description carries the full disclosure burden, and it does meaningfully characterize the user-facing behavior: nothing is bought, ordered or paid, no quote is guaranteed, and it is free. It also previews the returned content (who receives details, consent wording, and how the person confirms), which is exactly the trust-relevant context a consent flow needs. It still omits whether the tool itself has side effects, but the read-only intent is strongly implied.

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 usage cue ('Read first') is front-loaded, followed by the purpose and the guarantee caveats in a single compact block. The only mild redundancy is the trio 'bought, ordered or paid,' but it reinforces the key reassurance, so nothing genuinely wastes space.

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, no annotations, and no parameters, so the description must stand alone, and it sufficiently covers purpose, guarantees, and the shape of what is returned. For a simple 0-arg descriptive tool this is close to complete, with only minor room to be more explicit about the exact return structure.

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 there is nothing for the description to disambiguate. Per the baseline for 0-param tools, a 4 is appropriate; no syntactic or semantic gaps exist.

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 pairs a clear resource (the enquiry flow on SIM Only Deals Compare) with specific verbs (states, returns) and explicitly contrasts itself with the sibling submit_enquiry, which it says actually starts the enquiry. An agent can distinguish this documentation/read tool from the action tool without opening either schema. The framing is slightly indirect ('States plainly what submit_enquiry does') rather than a crisp 'describes X', which keeps it just below the top mark.

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 explicit ordering cue that this should be consulted before submit_enquiry, which is real usage guidance rather than a vague hint. It does not, however, spell out when-not-to-use it or name other alternatives, so it stops short of full when/when-not routing.

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