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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is carried structurally. The description adds genuinely new facts: it is free and needs no browser session, and it enumerates the kind of content returned. That is real value beyond the annotations, though nothing is said about response size, freshness, or whether results vary by app versus task.

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?

About 85 words with no filler; the trigger sentence, coverage caveat, cost note and the Timely action list each carry information. The opening sentence is an overlong colon-list that front-loads content types before the key instruction to call it first, so ordering could be tighter. No redundancy overall.

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 two-optional-parameter, no-output-schema lookup tool, the description covers what the returned guidance contains, when to call it, cost, and app coverage. The one real gap is not stating whether the response is shaped mainly by app, by task, or by both, which matters because callers may supply only one. Nothing else an agent needs in order to call it is missing.

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?

Schema description coverage is 100% and both parameters already document themselves (app name or Cotlet slug, default Timely; task in the user's words). The description only reinforces the Timely default and implies the task wording shapes the returned method. Baseline 3 is appropriate since the schema does the heavy lifting.

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 makes clear this returns how-to guidance for a named app: the applicable browser, the sign-in link, the click-by-click method, screens/menus/actions, notes, and any dedicated Cotlet tools. That distinguishes it from the cotlet_browser_* action tools and timely_* action tools well enough for selection. It is a content laundry list rather than a single crisp verb, which keeps it just below the top mark.

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?

'Call it before the first browser step in an app' gives an explicit trigger and ordering constraint. It also pre-answers the coverage question: any web app works, and apps outside the catalog fall back to the general method. It does not compare itself to cotlet_apps (the catalog lookup) or say when the guide can be skipped, so alternatives are only implied.

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