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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds meaningful context beyond them: it opens nothing by itself, it returns screens/buttons/fields to follow, and it must be paired with the browser tools to have any effect. Missing detail on whether the user must be logged into a browser session.

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 instructions are front-loaded, but the trailing sentence about Jotform's REST API and official MCP server ('checked 17 Oct 2026') is tangential to selecting or invoking this tool and reads as clutter rather than actionable guidance.

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 parameters and no output schema, the description carries the burden of describing the return value and does so ('returns how to do it in Jotform step by step (screens, buttons, fields)'). The only gap is that it doesn't say what happens if the user isn't in an authenticated Jotform session.

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 the baseline of 4 applies; there is no parameter information needed or missing.

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 states a specific action ('Create report in the user's own Jotform account') and then sharpens it by clarifying the tool only returns step-by-step instructions rather than performing the action. That clarification is essential given the imperative name, though the name/behavior mismatch costs a bit of crispness.

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 explicitly routes the agent: this tool produces the plan, then the agent executes with the cotlet_browser_* tools in the user's Jotform Cloud Browser. No explicit 'when not to use' or named alternative among the jotform_* siblings is given, which keeps it from a 5.

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