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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: the integration must be set up by the user in the app (not via this tool) and the call is 'Free' (no credit consumption), both of which affect agent planning.

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?

Two compact sentences with no filler; the return content is front-loaded and the constraint follows. The opening 'Whether the user has...' is a sentence fragment, which makes the first read slightly awkward, but nothing is wasted.

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?

There is no output schema, so the description takes on the job of explaining the return payload — connection status, last campaign, auto-send flag — and it does so. Authentication is handled by the schema and safety traits by annotations, leaving no critical gap for a zero-required-param read tool.

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?

Schema coverage is 100% and both parameters (uid, bearer_token) are documented as optional in the schema itself. The description adds no parameter-level information, so the baseline 3 applies — the schema carries all the weight here.

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?

The description names the resource (Outreach integrations: Instantly/Smartlead) and enumerates exactly what is reported: connection status, last-used campaign, and the auto-send setting. The verb is only implied by the title ('List'), so it is not a textbook verb+resource statement, and no sibling such as list_outreach_campaigns is called out, but the reported content is specific enough to distinguish it.

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?

It explicitly states a when-not case: connecting a tool happens in the UGC Agent app under Integrations and 'cannot be done here', which prevents the agent from attempting a write through this tool. It doesn't contrast itself against list_outreach_campaigns or update_auto_send, which would be needed for a 5.

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