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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, and the description's "Does not change anything" is consistent with them. It adds genuine context beyond annotations: what the payload contains (including transient "what needs attention now" counts) and what mcpUrl means operationally (adding this workspace as a separate connector, URL accepted once per client). It doesn't mention auth scoping or payload size, keeping it short of a 5.

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?

Purpose and usage are front-loaded, but the opening sentence is a comma-spliced run-on enumeration, and the "Related:" line repeats list_channels and get_website_cms already named in the body, plus get_brand_context and search_posts which are never explained. Roughly one sentence of the total is redundant.

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 read whose safety profile is already covered by annotations and whose return shape is covered by an output schema, the description supplies everything else an agent needs: when to call it, what it will learn, and which sibling to use instead for adjacent questions.

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 is 4. The description correctly implies no configuration is required to call it.

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 and resource ("Shows which Mark workspace you're acting in") and enumerates the concrete contents: role, timezone, members, sites, integrations, per-channel rows, and pending attention items. It explicitly distinguishes itself from list_channels and get_website_cms, so an agent can tell it apart from siblings without opening either schema.

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?

"Use it first in a session, or when switching tasks" gives an explicit trigger condition, and the description names both alternatives with the condition that selects each (list_channels for social accounts and channel rules, get_website_cms for website posts). This is when-to-use, when-not-to-use, and alternatives in one place.

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