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

No annotations are present, so the description carries the safety and behavior burden. Opening with 'Read' and enumerating returned channels, counts, and config makes the read-only nature clear and sets expectations about what the call returns. It does not cover auth, errors, or staleness, but for a simple getter this is a reasonable disclosure.

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 with a dash-delimited list of the key returned items; no filler or repeated structured information. It earns its length.

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?

The description covers the main output categories but, with no output schema, leaves response structure unspecified and does not clarify the required search_id or distinguish itself from related outreach siblings. Adequate for a straightforward getter, but there are real gaps.

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 only parameter, search_id, has no schema description (0% coverage), and the tool description does not explain what values it accepts or where they come from. Only the title's 'for a search' hints at its meaning, so the description adds little beyond the parameter name itself.

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?

Description starts with the action 'Read' and names the exact resource ('SDR outreach campaign') and the data it exposes: channels enabled, ready/queued/sent counts, and current content config. The title further scopes it to a search, distinguishing it from content-only and summary siblings. This is a specific, non-tautological purpose.

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 description implies the tool is for checking outreach status, but gives no explicit when-to-use guidance and does not mention alternative tools such as sdr_get_outreach_content, sdr_outreach_summary, or sdr_launch_outreach. An agent must infer selection from naming rather than from stated context.

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