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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description adds real behavioral value by disclosing the fallback: if nothing is saved, it returns a Brand Kit suggestion rather than empty data — that shapes how an agent interprets the response.

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?

One front-loaded sentence that states the resource and the fallback, plus a short safety tag. The trailing 'Read only.' mildly duplicates readOnlyHint but is a cheap reinforcement rather than bloat.

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 rich annotations, the description carries only the burden of telling the agent what content comes back, which it does (keywords, places, competitors, or Brand Kit suggestion). Only the distinction from the save sibling is left implicit.

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. Baseline 4 applies; the schema is trivially complete.

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?

States a specific verb (Read) and the concrete resource contents: saved keywords, places, competitors, or a Brand Kit suggestion. It is clear enough to distinguish from soclo_conversations_watch_save, though it never names the write counterpart explicitly, relying on 'Read only' as the differentiator.

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?

The 'when nothing is saved yet' clause describes the fallback return, not an explicit call condition, and no alternative tool is named. The implied usage (read current watch config before scanning) is inferable but never stated.

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