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

The definition is consistent with the annotations (readOnlyHint=true, destructiveHint=false) and reinforces them with the concrete statement that the tool "opens nothing" and only returns text. It adds the integration-context nuance that mHelpDesk only syncs with QuickBooks and Google Calendar plus a freshness stamp, though it stops short of describing response format or how current/stable the returned steps are.

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 critical correction — that this returns instructions rather than creating anything — is front-loaded in the first sentence, and the follow-up browser step comes next. The trailing API/sync note is useful context but makes an already dense block longer, and the 'checked 9 Nov 2026' stamp reads awkwardly.

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 zero-parameter guidance tool with no output schema, the description covers what it returns, that it has no side effects, and which tools perform the actual work. An agent has everything needed to call it correctly and to know what to do with the result.

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 to disambiguate; the baseline for a parameterless schema applies. The description could have noted that no account or invoice data is passed in (all detail comes from context), but no parameter meaning is missing.

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?

"Create invoice in the user's own mHelpDesk account ... Returns how to do it in mHelpDesk step by step (screens, buttons, fields) and opens nothing by itself" states exactly what the tool produces and explicitly negates the action implied by its name. It distinguishes itself from the sibling create_* tools by making clear it is a guidance tool, not a mutating one.

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 the full workflow: call this to get steps, "then do it with the cotlet_browser_* tools in the user's mHelpDesk Cloud Browser." It also justifies why the browser path is required ("mHelpDesk publishes no public API, webhooks or Zapier app"), so an agent knows there is no direct-API alternative to look for.

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