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

Annotations already declare openWorldHint=true, readOnlyHint=false and idempotentHint=false, so the write/external nature is partially covered. The description adds value beyond them by disclosing the human follow-up channel and the consent constraints (user-provided contact details only, confirm before sending) — a side-effect and privacy posture the annotations cannot express.

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 sentences, front-loaded with what the tool does and what happens next, then the constraints. Every sentence carries a distinct obligation with no filler.

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?

Covers purpose, preconditions, consent handling and the out-of-band outcome, which is what an agent needs for a low-complexity, flat-schema submission tool. It says little about failure or duplicate-submission behavior, but nothing essential is missing for correctness.

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 all six fields including optional phone, message and business are already documented. The description only adds a provenance rule for the contact details ('details the user has given you'), not new field semantics, so the baseline 3 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?

States a specific verb and resource ('sends the user's request for help fixing their website') plus the destination and follow-up channel (Soofi Digital's team contacting by email or WhatsApp). This clearly distinguishes it from the sibling audit_website, which analyzes a site rather than forwarding a request to a human team.

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?

Gives an explicit gate: 'Only use when the user explicitly asks for help or for Soofi Digital to contact them, and only with contact details the user has given you for this purpose.' It also imposes a procedural prerequisite ('Confirm the details with the user before sending'), leaving the agent with no ambiguity about when to call it.

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