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

The annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false and idempotentHint=true; the description reinforces this by stating it 'opens nothing by itself,' which correctly resolves the tension between the destructive-sounding name and the read-only annotation. It also discloses the shape of what comes back (screens, buttons, fields). It stops short of describing format, length or failure behavior of that guidance.

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 behavior and the hand-off to cotlet_browser_* are front-loaded and earn their place. The trailing sentence about 123FormBuilder's REST API v2 and token login adds no actionable information for an agent using this tool and reads as filler that dilutes the message.

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?

The tool is simple (no params, no output schema), but an agent still needs to know which form the instructions apply to, since nothing in the schema supplies an identifier. The description also does not say whether the returned guidance is generic or account-specific. The irrelevant API-version note occupies space that could have closed these gaps.

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 no schema content for the description to explain. One residual point is unaddressed: with no inputs, the form to act on must be resolved from conversation, and the description does not say so.

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 names the specific resource (a form in the user's own 123FormBuilder account) and clarifies an otherwise misleading name by stating it returns step-by-step instructions rather than performing the deactivation. It also distinguishes itself from the cotlet_browser_* tools that actually carry out the action. The remaining ambiguity is that it never says how the target form is identified, which matters for a tool named 'deactivate_form'.

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 gives a clear sequence: call this to get the steps, then execute them with the cotlet_browser_* tools, and it explicitly states it opens nothing by itself. However, it offers no guidance on prerequisites or alternatives — e.g., when to use this versus cotlet_app_guide, or whether a list_forms call is needed first to pick the form. Usage is implied through the sequencing rather than spelled out.

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