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

The description discloses substantial behavior beyond the annotations: it creates a seeker account when the email is new, leaves the hunt pending when an account already exists, sends emails on matches, and defers phone sharing to the website. It does not, however, address the destructiveHint=true annotation — nothing explains what is overwritten or destroyed on a save — nor does it confirm the idempotentHint behavior.

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 action is front-loaded, which is good, but the passage runs five sentences and wanders into account-lifecycle detail. The final sentence — 'Verify your phone so matching partners can reach you' — is user-facing marketing copy addressed to the seeker, not guidance for an agent invoking the tool, and does not earn its place.

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 25-parameter mutation with no output schema, the description covers the critical non-obvious behavior: consent prerequisite, phone exclusion, account creation and the pending state. Missing pieces are the destructive semantics flagged by annotations and any indication of what the call returns, but overall it is complete enough to call safely.

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 96%, so the schema already documents nearly every parameter. The description's nod to consent ('This is not consent to share a phone number' is already in the schema) and the no-phone rule add little that the schema lacks, so the baseline 3 for high-coverage schemas applies.

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 opening sentence states a specific verb and resource ('Saves a hunt alert for this query') and goes further to describe the full flow — email sharing, matching notifications, account creation. However, it never names or contrasts with the closest alternative path (e.g., guided_rental_questionnaire or search_rentals), so an agent gets a clear purpose but no sibling routing.

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 preconditions ('Requires consent true', 'Does not accept a phone number') and describes what happens to an email that already has an account, which implies when the tool is and isn't applicable. But there is no explicit when-to-use-vs-alternative guidance and no stated exclusions relative to sibling tools, so usage is inferred rather than directed.

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