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

With no annotations, the description carries the safety profile itself by declaring 'Read-only' up front, and it previews the shape of the returned data (status, channels, counters). It stops short of describing pagination, scoping, or whether inactive processes are included.

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?

A single short sentence with the read-only constraint front-loaded and zero filler. Every clause adds information: safety, resource, scope, and returned fields.

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 list tool with no output schema, the description supplies the key facts an agent needs: it is read-only, workspace-scoped, and yields status/channels/counters. A note on result size or ordering would make it fully self-sufficient.

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 to disambiguate; the baseline for a no-parameter schema applies. The description helpfully notes the scope is the whole workspace rather than a filtered subset.

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+resource: lists the workspace's SDR outreach processes, with the UI anchor ('Sales Process page') and the returned fields (status, channels, counters) named. It is distinguishable from siblings like sdr_get_outreach or sdr_outreach_summary, though it never explicitly says how it differs from them.

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?

Calling it a workspace-wide listing implies when it applies, and 'Read-only' signals it is a safe discovery call, but there is no explicit when-to-use or when-not guidance and no sibling is named as an alternative.

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