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

Beyond annotations, the description states plainly that the tool opens nothing by itself, returns screen/button/field instructions, and explains why a direct API route is unavailable (Enterprise-only tokens, Threat Intelligence-oriented endpoints). That is real behavioral context the readOnly/openWorld annotations do not convey.

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?

Core behavior is front-loaded in the first two sentences, but the third sentence about Feedly's REST API, Enterprise token limits, and Threat Intelligence endpoints is a dated aside that adds bulk without helping the agent invoke the tool.

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 no-parameter guidance tool the description covers the mechanism and handoff to browser tools, but it never clarifies what the returned text contains (single guide vs. article list) or how the agent should interpret the result, which matters because the name implies article data is returned.

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 has zero parameters, so the baseline is 4; the schema's additionalProperties:false already communicates a parameterless call and the description correctly offers no parameter guidance.

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 first sentence claims the tool lists articles in the user's Feedly account, but the second sentence reveals it actually returns a step-by-step guide and opens nothing itself. That is an honest disclosure, but the name/title and opening line point to a different function than what the tool performs, leaving the agent to reconcile two purposes.

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 tells the agent the follow-on action: use cotlet_browser_* tools in the user's Feedly Cloud Browser to actually perform the listing. It never distinguishes this from feedly_search_articles or feedly_list_feeds, nor states when fetching a guide is preferable to acting directly.

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