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

Annotations indicate mutations (readOnlyHint=false) and idempotency (idempotentHint=true). The description adds behavioral context: saves data only after consent, handles email format errors with re-questioning, and provides an onboarding link after save. No contradictions with annotations.

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 a single paragraph with the main action at the start, then includes a structured privacy notice. It is not overly verbose but could be better organized. Every sentence adds value.

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 no output schema, the description covers what happens after save (onboarding link), input validation, privacy requirements, and consent procedure. It is complete for a simple lead capture tool.

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%, so baseline is 3. The description adds meaning: email requires prior consent, interest is optional up to 500 characters, and email format error triggers re-questioning. This is good but not extraordinary.

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 clearly states the tool's purpose: saving email and optional interest for users who want to continue consultation. It distinguishes from sibling tools like assess_admissions_fit or search_mentors, which serve different functions.

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?

Explicitly instructs to call only when user explicitly wants to be contacted, and provides a detailed privacy notice including consent requirements, data collection purpose, retention period, and deletion rights. This gives clear usage context.

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