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

The claim that it "opens nothing by itself" is consistent with readOnlyHint=true and adds meaningful framing beyond the annotation. The API note (official API exists but only on the top plan, checked 20 Oct 2026) is genuinely useful extra context. What is not disclosed is the actual response shape or whether pipeline data is ever returned, leaving the core behavior ambiguous.

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 constraints are front-loaded, which is good, but "from ChatGPT, Claude or any AI agent" is filler that consumes prime position. The sentence also chains three distinct ideas (step-by-step return, no side effects, browser follow-up) into one dense run-on, and the trailing API-plan note is grammatically disconnected.

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 and zero parameters, the description carries the full burden of explaining what comes back, and it does so only vaguely ("screens, buttons, fields"). The browser handoff and API-availability caveat are covered, but the mismatch between the name and the described return leaves an agent unsure what to expect.

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 no parameters, so the baseline of 4 applies. There is nothing parameter-related the description needs to add, and it does not waste space restating empty input.

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 opening clause names a specific verb and resource ("List job pipeline in the user's own Manatal account"), which separates it from the mutation-oriented Manatal siblings. However, the next clause says it "Returns how to do it in Manatal step by step (screens, buttons, fields)", which reframes the tool as a guidance provider rather than a lister. An agent reading only this cannot tell whether it will receive pipeline data or instructions.

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 states the tool "opens nothing by itself" and that the actual work must be done "with the cotlet_browser_* tools in the user's Manatal Cloud Browser", which is a clear use-then-follow-up workflow. It is missing any statement of when NOT to use this tool (e.g. when the official API path is available), so it falls short of a 5.

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