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

With no annotations, the description carries the full burden. It usefully reveals this launches an interactive browser session rather than returning data, and that a projectId scopes to one catalog's previews. However, it is silent on the token/auth flow (the token param comes from poll_access) and whether the open action has side effects.

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?

Front-loads the purpose in the first clause and stays to three short sentences with little waste. The parenthetical about projectId is slightly awkwardly placed but not harmful.

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?

Output schema exists, so return values need not be explained, and the core function is conveyed. But for a no-annotation tool the omission of auth/token behavior and interaction with poll_access leaves an agent without the context needed to invoke it in restricted sessions.

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?

Schema coverage is 100%, so baseline is 3. The description only touches projectId ('loads one catalog's previews') and ignores the token parameter entirely, while the claim 'Takes no arguments' is misleading given two optional params exist.

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+resource: 'Open the hosted preview catalog browser', then enumerates what it contains (catalogs, previews with search, published render). This is distinguishable from list/render siblings, though it does not explicitly name an alternative like catalog_list_previews or ui_builder_open.

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?

No when-to-use or when-not-to-use guidance relative to the many catalog_* siblings. The note that it 'Also opens from the ChatGPT/Codex sidebar' describes an entry point, not a selection condition for the agent.

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