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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real value: it explicitly states the tool navigates nothing and returns procedural content instead of data. The note that iSpring Learn's REST API requires the Business tier and that no official MCP server exists explains why browser automation is the follow-up, which is useful context an agent cannot get from annotations.

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 workflow is front-loaded and readable, but the full 'iSpring Learn (iSpring LMS)' string is repeated three times and the 'from ChatGPT, Claude or any AI agent' phrasing is filler. The dated API-availability footnote is useful but is placed at the end where it dilutes the actionable part.

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 covers what an agent needs: what the call returns (step-by-step UI instructions, not data), that it has no side effects, and which tool family continues the task. Only the absence of an explicit 'use this when…' clause and sibling comparison holds it back.

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 there is nothing for the description to explain beyond the input schema. Baseline 4 applies; no parameter-level ambiguity exists.

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 name and title say 'list courses', but the description actually describes a how-to/guidance tool that 'opens nothing by itself' and returns 'step by step (screens, buttons, fields)' instructions. That is an important distinction an agent would want stated up front rather than buried in sentence two, and no sibling (e.g. ispring_list_enrollments) is named to disambiguate scope.

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 gives a clear workflow: call this first to get the procedure, then execute it with the cotlet_browser_* tools in the Cloud Browser. It lacks any explicit when-not-to-use or a named alternative among the ispring_* siblings, which keeps it out of 5 territory.

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