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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds that campaigns come from an external connected account (Instantly/Smartlead) and are 'Free', plus the accepts_leads filter nuance. It does not describe pagination behavior or result shape, but the schema's limit/cursor largely cover that.

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 short sentences, front-loaded with the core action and scope. No filler; each sentence adds a distinct piece of information, though it is sparse rather than rich.

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 read-only list tool with well-documented parameters (83%) and no output schema, the description covers purpose, source accounts, and the key filtering nuance. It is sufficient to call correctly, though it omits any note on what fields campaigns return.

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 description coverage is 83%, so the schema already documents provider, limit, cursor, search, uid, and bearer_token. The description only reinforces provider (Instantly/Smartlead) and the accepts_leads concept; with high schema coverage, baseline 3 is appropriate.

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 'List' and resource 'campaigns' scoped to the user's connected Instantly or Smartlead account, so the agent knows exactly what is being returned. It does not explicitly name the sibling (list_outreach_integrations, send_leads_to_campaign) it complements or differs from, so sibling differentiation is only implied.

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 'accepts_leads=true can receive leads' line gives useful context that this list is consulted before sending leads, implying a workflow with send_leads_to_campaign. However, there is no explicit when-to-use/when-not guidance or named alternative, leaving selection to inference.

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