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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: it explicitly says it 'opens nothing by itself' and that the actual action must be performed via cotlet_browser_* tools, which prevents an agent from assuming the invoice is sent. The trailing note about Pennylane's public REST API is informational but not behavioral.

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 core behavior and the browser follow-up are front-loaded and clear. The final sentence about Pennylane's official API, scopes and a check date is tangential to invoking this tool and dilutes the message.

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?

There is no output schema, and the description compensates by stating what is returned (step-by-step screens, buttons, fields). Combined with the explicit statement that nothing is opened automatically and the pointer to browser tools, an agent has enough to call it correctly; only sibling differentiation is missing.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies no inputs are needed to obtain the guide.

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 does state the resource (Pennylane invoice sending) and clarifies that the tool returns step-by-step instructions rather than performing the action. However, the name and title say 'Send invoice', which conflicts with the actual behavior of only producing a guide, and the description never distinguishes this from the sibling pennylane_create_customer_invoice or cotlet_app_guide.

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 gives a follow-up path ('then do it with the cotlet_browser_* tools in the user's Pennylane Cloud Browser'), which is useful sequencing guidance. It does not say when to prefer this over pennylane_create_customer_invoice or cotlet_app_guide, nor any prerequisites or exclusions.

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