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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so the bar is lower, yet the description adds non-obvious behavior: it returns procedural UI instructions and performs no action itself. That is exactly the context an agent needs to avoid assuming it mutates anything or returns data. It stops short of describing the instruction payload's structure or what happens if Brand24 isn't configured.

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?

Two sentences, front-loaded with the purpose and the follow-up action, but they carry filler ('from ChatGPT, Claude or any AI agent') and a cryptic trailing fragment ('Brand24's official API: Yes') that consumes space without informing invocation.

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, no output schema and full annotation coverage, the description supplies enough: what it returns (step-by-step screens/buttons/fields), what it does not do (opens nothing), and the required follow-up tool family. The only gap is the ambiguous 'official API: Yes' note, which an agent cannot act on.

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 schema has zero parameters with 100% coverage, so the baseline is 4; the description correctly implies no inputs are needed. It adds no parameter guidance because none exists, which is appropriate.

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 states a concrete resource (project stats in the user's own Brand24 account) and clarifies the actual output — a step-by-step guide of screens, buttons and fields rather than the stats themselves. The headline verb 'get' is slightly at odds with the real behavior (returns instructions), but the second sentence resolves it and separates this tool from the cotlet_browser_* execution tools.

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 an explicit sequencing rule: this tool 'opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Brand24 Cloud Browser', which is real when/how guidance. It does not explain when to prefer this instruction tool over the other brand24_* siblings (e.g. brand24_list_mentions), and the teaser 'Brand24's official API: Yes' is unexplained, leaving the alternative path ambiguous.

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