invoices_send_estimate

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

Annotations indicate readOnlyHint=false, but the description adds no behavioral context. It fails to disclose that action selects the delivery channel (email, SMS, or manual), that sending may trigger notifications, or any permission requirements. It carries no disclosure beyond the 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?

At two words, the description is under-specified rather than concise. It omits essential context and provides no front-loaded useful information, making it far too uninformative for an agent.

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 8 parameters, 4 required, and no output schema, the description is wholly inadequate. It does not explain what the action parameter controls, what happens on send, or what response to expect. An agent would lack critical information to call this tool 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?

The input schema already describes all parameters with 88% coverage, so the description does not need to redundantly explain them. However, it also adds no extra meaning about nuances like the 'action' enum or 'sentFrom' conditions. Baseline 3 is appropriate given high schema coverage.

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 'Send Estimate' names a verb and resource but is essentially a restatement of the tool name. It does not specify the sending channels (email/SMS) or differentiate from similar tools like invoices_send_invoice, leaving the agent without enough information to pick it correctly.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention conditions, exclusions, or related tools (e.g., invoices_send_invoice for invoices), so an agent cannot determine when this tool is appropriate.

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