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

Adds real behavior beyond the annotations: the confirm-per-call default and its override, the external-reach warning, the API key requirement, and the post-send status outcomes (Customer Approved/Declined, e-signature on approval). Some redundancy (external reach/confirmation stated twice) keeps it from a 5, but it substantially enriches an annotation set that only declares non-read-only and open-world.

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?

Purpose is front-loaded, but the passage is padded: 'by email or text' is stated twice and the confirmation requirement is repeated across two sentences. Information is useful but not tight.

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 send/mutate tool with full schema coverage and annotations covering the safety profile, the description is largely complete: recipients, channels, outcomes and prerequisites are covered. No output schema exists, but the description explains the resulting status, leaving little an agent would need to call it correctly.

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 the schema already documents all six parameters. The description reinforces a few ('Several email addresses are allowed', 'with the options you pick and an optional subject and message') but adds no syntax or format detail beyond what the schema provides, 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+resource ('Send an estimate') with scope detail: chosen options, email/text/both, optional subject and message. An agent can clearly distinguish it from siblings like housecall-pro_send_invoice or housecall-pro_create_estimate without opening the schema.

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 clear usage context including confirmation behavior ('By default you confirm each call; you can switch that off') and the API key prerequisite. However it does not explicitly route the agent away from alternatives such as send_invoice, so it stops short of full when/when-not guidance.

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