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 thoroughly. It discloses that this is not a purchase or guaranteed quote, that consent must match the exact quoted statement, that a confirmation token is required, and that providers only see the enquiry after the person clicks an email link.

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 long but dense; every sentence contributes workflow logic, consent requirements, or behavioral caveats. The step labels and quoted consent line are essential content, with no redundant or filler phrasing.

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, yet the description explains what Step 1 returns (summary, consent line, confirmation token) and what Step 2 produces (email link before provider access). This gives the agent everything needed to invoke the tool correctly and understand downstream effects.

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 100%, but the description adds substantial meaning: answers must be keyed by field keys from enquiry_fields, consent must be true and match the specified text, and confirmation is the token from Step 1. This directly links each parameter to the two-step workflow.

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 states the action ('submits an enquiry to GPA Grade Compare'), the target ('human providers'), and the key exclusions ('NOT a purchase, NOT a guaranteed quote'). The two-step nature is named in both title and description, distinguishing it from sibling tools like enquiry_describe and 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?

Provides an explicit step-by-step procedure: Step 1 validates and returns a summary/confirmation token; Step 2 is used only if the person agrees, with the same answers plus the token. It also states the prerequisite of using field keys from enquiry_fields and clarifies when the tool should not be used.

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