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, and the description is consistent with them rather than contradicting them — it explains the read-only nature by saying the tool 'opens nothing by itself.' It adds genuine context beyond the annotations: the return value is screens, buttons and fields, and the reason browser automation is required ('Clear Estimates publishes no public API'). It does not describe instruction granularity or failure modes.

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 the action and the key caveat that nothing is opened. The clause 'from ChatGPT, Claude or any AI agent' is marketing filler that adds no decision-relevant information and could be cut. Otherwise the wording is tight and purposeful.

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 no parameters and no output schema, the description carries the full burden and does explain what comes back (step-by-step screens, buttons, fields) and what to do next. The absence of an output schema is offset by that description of the return content. What is missing is any notion of scope — which invoice fields or prerequisites matter — but for a zero-input guidance tool this is close to complete.

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 for a parameterless tool applies, and the description correctly implies no inputs are needed. No further credit or penalty is warranted.

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 states a specific verb and resource ('Create invoice in the user's own Clear Estimates account') but immediately qualifies it: the tool returns step-by-step instructions and 'opens nothing by itself.' That resolves the mismatch between the imperative name and the read-only annotations. It stops short of distinguishing itself from the other clear_estimates_* siblings by name, so an agent must infer that this is a guidance tool rather than the action itself.

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?

The description gives an explicit workflow: call this to get the steps, 'then do it with the cotlet_browser_* tools in the user's Clear Estimates Cloud Browser.' That is clear context for how and when to use it. It does not state when not to use it, or which clear_estimates_* sibling to pick for a different resource, so the routing among siblings is only partly covered.

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