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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds real value beyond that by stating 'opens nothing by itself', disclosing that the return value is procedural instructions rather than data, and explaining the API access caveat ('read-only'). The one gap is that it never describes the shape or length of the returned steps.

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 description is one run-on construction stitched together with semicolons, and it opens with boilerplate ('from ChatGPT, Claude or any AI agent') that adds no selection value. The crucial fact — that the tool returns instructions instead of menu items — is buried in the middle rather than front-loaded.

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-argument, read-only tool with full annotation coverage, the safety and read-only story is complete, and the handoff to cotlet_browser_* is spelled out. What is missing is any indication of what the returned steps look like and, more importantly, how this differs from toast_list_menus and toast_86_a_menu_item, which an agent must choose between.

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 nothing for the description to disambiguate. It rightly says nothing about inputs, though it does not explicitly say 'takes no arguments'.

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 first sentence names a specific verb and resource (list menu items in the user's Toast account), but the second sentence reveals the tool does not actually list anything — it 'Returns how to do it in Toast step by step (screens, buttons, fields)'. An agent reading the name and title would expect menu data, so the true function is only clarified mid-description. It also never distinguishes itself from the very similar siblings toast_list_menus and toast_86_a_menu_item.

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 does say what to do next — 'then do it with the cotlet_browser_* tools in the user's Toast Cloud Browser' — which is genuine routing guidance to a tool family. However it gives no explicit when-to-use or when-not-to-use versus toast_list_menus or toast_86_a_menu_item, and no prerequisite/ordering statement such as 'call this first, before any browser action'.

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