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 usefully adds that the call 'opens nothing by itself' and hands off to browser tools, but the shape of what comes back (screens/buttons/fields) is only sketched, and the trailing API note with a check date adds unresolved noise rather than behavior.

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 text is padded with audience boilerplate ('from ChatGPT, Claude or any AI agent') and an API aside ('REST API v2 with token login (checked 23 Oct 2026)') that does not help an agent invoke this tool. The middle sentence also packs three ideas at once.

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?

With no output schema, the description carries the burden of explaining return values, and it only roughly does so ('step by step (screens, buttons, fields)'). For a zero-parameter, read-only tool the complexity is low, so this is close to adequate, but the ambiguity about whether forms data is returned leaves a meaningful gap.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The description does not mislead about inputs, though it also adds nothing here.

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?

It opens with a specific verb+resource ('List forms in the user's own 123FormBuilder account'), but the next sentence reverses that expectation by saying it 'Returns how to do it in 123FormBuilder step by step (screens, buttons, fields) and opens nothing by itself.' An agent cannot reliably tell whether it receives form records or a procedural how-to, which is a real ambiguity given the name says 'list_forms'.

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?

There is genuine routing guidance: the tool supplies steps and then the agent should 'do it with the cotlet_browser_* tools in the user's 123FormBuilder Cloud Browser.' However, there are no exclusions and no guidance on when to prefer this over siblings like 123formbuilder_list_submissions or over the mentioned REST API path; the API sentence is dropped in without telling the agent what to do with it.

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