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 safety is covered. The description adds the non-obvious behavior that the tool "opens nothing by itself" and only returns screens/buttons/fields, which prevents an agent from assuming an export is executed. The stray line "Anaplan's official API: Yes." is cryptic and adds no usable behavioral signal.

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 information is front-loaded and useful, but several phrases dilute it: "from ChatGPT, Claude or any AI agent" is boilerplate, and "Anaplan's official API: Yes." is telegraphic and ambiguous. The instruction flow (returns steps, then use browser tools) could be tighter.

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 guide tool the description covers the return content reasonably (screens, buttons, fields) and the handoff. It does not tell the agent what context the user must supply — model name, export name, workspace — which is the main missing piece for invoking it correctly.

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?

Zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not need to compensate for any schema gap.

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 ("Run export ... in the user's own Anaplan account") and, crucially, clarifies that it returns step-by-step instructions rather than performing the export. It does not explicitly contrast itself with anaplan_run_import or anaplan_run_process, but the resource noun makes the distinction self-evident.

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?

Explicitly routes the agent: this tool produces the how-to, then "do it with the cotlet_browser_* tools in the user's Anaplan Cloud Browser." That names the alternative and the handoff condition. It lacks any when-not guidance or prerequisites (e.g., needing a model/export name first).

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