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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds the genuinely non-obvious trait that the tool "opens nothing by itself" and only returns instructions, preventing a naive agent from assuming the listing occurs. It also discloses that Weezevent's REST API is partner-only and cannot read orders, which explains the tool's existence. Auth requirements and the actual response shape are not spelled out.

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 purpose is front-loaded, but the opening clause "from ChatGPT, Claude or any AI agent" is marketing boilerplate that earns no place, and the second sentence is a run-on stacking three separate ideas behind a semicolon. The API footnote is valuable but reads as an appended parenthetical with a stale-looking future date.

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, no-output-schema guidance tool, the definition covers what it returns (screens, buttons, fields), what it does not do, and which tools continue the workflow. It only lacks a hint about what the step-by-step output structurally looks like, which an agent would need to chain into the browser tools.

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 the baseline is 4 and there is no parameter meaning the description could add or omit. The description correctly indicates the only implicit scoping ("user's own account") since no account argument is exposed.

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 and resource ("List orders") scoped to "the user's own Weezevent account," which distinguishes it from siblings like weezevent_list_attendees and weezevent_list_events by object type. The second sentence complicates it by revealing the tool returns step-by-step guidance rather than orders, which muddies but does not obscure the intent.

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 a follow-up path ("then do it with the cotlet_browser_* tools in the user's Weezevent Cloud Browser") and implies when the tool is needed by noting the official API does not cover orders. It never explicitly says when not to use it or how it relates to other weezevent_* tools that might also touch order data.

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