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

The annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), and the description adds the non-obvious behavioral fact that the tool opens nothing by itself and only returns screens/buttons/fields guidance that must be executed via browser tools. That is exactly the context an agent needs before invoking. It stops short of describing output format or length.

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 operational content is front-loaded, but the audience phrase 'from ChatGPT, Claude or any AI agent' is filler, and the closing note about Freshsales having a REST API but no official MCP server (with a check date) is tangential to invoking this tool and dilutes focus.

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?

For a zero-parameter, read-only guidance tool with no output schema, the description covers what it returns, that it performs no side effects, and what the agent should do next. Only the precise shape of the returned steps is left implicit, which is a minor gap.

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?

There are zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-arg tool applies. The description does not add spurious parameter-like detail, which is appropriate here.

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 names a specific verb+resource (list overdue tasks) and scope (the user's own Freshsales account), and it distinguishes the resource from siblings like contacts or pipelines. The one ambiguity is that it frames the output as step-by-step instructions rather than task data, so an agent must read to the second clause to learn it is a guide, not a data fetch.

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 gives clear usage context ('from ChatGPT, Claude or any AI agent') and an explicit next-step workflow: call this first, then act with the cotlet_browser_* tools in the Freshsales Cloud Browser. It does not offer explicit when-not guidance or name an alternative for retrieving the same data another way.

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