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

Goes meaningfully beyond the annotations by disclosing that the tool performs no browser action on its own and that execution is deferred to the cotlet_browser_* family. The note that Polarsteps has no public API or official MCP server is useful scope context. It stays consistent with readOnlyHint/idempotentHint/destructiveHint=false rather than contradicting them.

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 key constraint (returns instructions, opens nothing) is front-loaded, but the third sentence is a dangling fragment ("Polarsteps's official API:") that trails off without a predicate and carries an oddly dated provenance check. The middle clause is a run-on joining "returns...", "opens nothing", and "then do it with..." in one sentence.

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 zero parameters and no output schema, the burden is light, and the description does explain the kind of content returned (screens, buttons, fields). However, it does not say how detailed or structured that guidance is, nor whether it names the specific browser tools to use next, leaving the agent to infer the handoff.

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 semantic gap to fill. Nothing in the description is needed to call it correctly.

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 and resource ("List trips in the user's own Polarsteps account") and immediately clarifies the non-obvious nature of the result: it returns step-by-step instructions rather than trip data. That clarification is critical because the name/title imply data retrieval. It falls short of 5 because it never distinguishes itself from the sibling cotlet_app_guide, which plausibly offers the same kind of guidance.

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?

Gives clear sequencing guidance: call this first, then "do it with the cotlet_browser_* tools in the user's Polarsteps Cloud Browser," which is exactly the routing an agent needs. It also states the negative behavior ("opens nothing by itself"). It does not explain when to choose this over cotlet_app_guide or via which account context, so no explicit alternatives comparison.

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