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

Annotations already declare this is a non-readonly, open-world, non-idempotent write. Beyond that, the description discloses a precondition (user consent) and the failure behavior: on non-delivery it says NOT SENT and returns the quote, a book-a-call link and an email address. That failure-path disclosure is genuinely useful; what remains unstated is retry/idempotency semantics for a non-idempotent send.

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?

Three tightly packed sentences, zero filler, and the identifying constraint ('only tool that takes contact details') plus the precondition are front-loaded. Every clause carries information the agent needs before invoking.

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?

With no output schema, the description compensates by describing both the success behavior (request sent to the ELC team) and the failure return (NOT SENT plus quote, book-a-call link, email address). Combined with full schema coverage and annotations, an agent has enough to decide, call, and interpret the result.

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 description coverage is 100%, so every parameter is already documented in the schema with required flags and allowed values (packages, add-ons). The description only gestures at the payload ('chosen package and add-ons') and 'contact details' without adding format, constraint, or interaction semantics, so the baseline 3 is appropriate.

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 a specific verb (sends a request for a written partnership offer), the resource (ELC Conference 2027 partnership offer), and the payload (chosen package and add-ons). It also explicitly differentiates itself from siblings: 'The only tool that takes contact details,' which no other tool in the list claims.

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?

It states a clear gating condition — call only after the user has agreed to send name, email and company — which is exactly the when-to-use guidance an agent needs. It does not, however, name the alternatives to use instead when that consent is absent (e.g., quote_partnership or get_partnership_guide), leaving the fallback selection to inference.

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