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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description reinforces with 'Does not change anything.' It adds a useful trigger ('first in a session') but doesn't disclose return size or pagination, though an output schema presumably covers payload shape.

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?

Three tight sentences: purpose/payload first, then trigger, then non-mutation note and related tools. The parenthetical payload list is dense but earns its place by telling the agent what it will get.

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 zero-parameter read with an output schema and full annotation coverage, the description provides everything needed: what it returns at a high level, when to invoke it, what it does not do, and which siblings handle adjacent needs.

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?

Zero parameters, so baseline is 4. There is nothing to document and the description correctly implies a parameterless call with no filtering requirement.

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 exact payload (role, timezone, members, sites, integrations, per-channel status, attention items). An agent immediately knows this is a workspace-state read, distinct from the many list_*/get_* siblings.

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?

Explicit guidance: 'Use it first in a session, or when switching tasks.' It also names the alternative for a related need: 'For which social accounts are connected and each channel's rules, call list_channels.' When-and-alternative routing is fully specified.

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