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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with the specific, useful disclosure that the tool 'opens nothing by itself' and only returns screens/buttons/fields text. That resolves the tension between an action-sounding name and a read-only annotation. It doesn't say how the guide is scoped (e.g., whether it can target a specific event ID, given there are no parameters).

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 operative sentence (returns step-by-step guidance, opens nothing, then use cotlet_browser_* tools) is front-loaded and earns its place. The 'from ChatGPT, Claude or any AI agent' clause and the trailing API-version-and-date sentence are filler that lengthens the definition without changing agent behavior, and the 'checked 31 Oct 2026' date reads as noise.

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-only tool with no output schema and full annotation coverage, everything an agent needs to select and call it is present: what it returns, that it performs no action, and which tools to use next. The only gap is whether the guide can be scoped to a particular event, which zero parameters leave unaddressed.

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 and the baseline of 4 applies. The description adds no parameter-level meaning, but none is needed.

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 the resource (a Humanitix event) and clarifies that the tool returns a step-by-step procedure rather than performing the duplication, which is the crucial detail an agent needs. However, the name and title ('Duplicate event') imply an action, so the agent must read past the first clause to learn this is a guide. The final sentence about Humanitix's API surface is context, not purpose.

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 clearly routes the agent: get the steps here, then execute them with the cotlet_browser_* tools in the Humanitix Cloud Browser — a concrete follow-on workflow rather than an inference. It also implicitly excludes itself from doing the work ('opens nothing by itself'). It does not name when to prefer this over related siblings such as cotlet_app_guide or humanitix_create_discount_code.

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