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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds genuinely non-obvious behavior: it performs no action itself, it returns step-by-step instructions (screens, buttons, fields), and the account is limited to SingleOps' Lead Entry API. That last point explains a real capability boundary. It still does not say what the returned guidance looks like in structure, which keeps it below 5.

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?

Sentences are run-on and mix marketing ('from ChatGPT, Claude or any AI agent'), an instruction to use other tools, and a quoted API fact in a way that muddles the core message about what is actually returned. The key clarification ('opens nothing by itself') is buried mid-sentence rather than front-loaded.

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 must carry the meaning of the return value, and it does state that it returns step-by-step SingleOps instructions plus a pointer to cotlet_browser_* tools. What is missing is any indication of the shape or scope of that guidance, leaving the agent to discover it by calling.

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 disambiguate and the baseline of 4 applies. No misleading parameter claims are made.

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 verb+resource ('List jobs in the user's own SingleOps account') is specific, but the description then reframes the tool as something that 'Returns how to do it in SingleOps step by step' and 'opens nothing by itself' — so the agent cannot be sure whether this returns job data or a how-to guide. It never explicitly differentiates itself from siblings like singleops_list_proposals or cotlet_app_guide.

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 does name the follow-up path ('then do it with the cotlet_browser_* tools in the user's SingleOps Cloud Browser'), which gives an implied when-to-use and a concrete next step. However there is no explicit statement of when NOT to use it, or why an agent would pick this over cotlet_app_guide or the other singleops_list_* tools.

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