List your campaigns with ID, name, status (draft/running/paused), description and lead counts. Use this to obtain campaign_id when adding leads, generating messages or approving drafts.
| Name | Required | Description | Default |
|---|---|---|---|
| status | No | Filter by campaign status. Optional. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds that the tool lists specific fields (ID, name, status, description, lead counts) and provides use case context. No contradictions.
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 sentences, front-loaded with the purpose, and immediate usage guidance. No unnecessary words. Every sentence earns its place.
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 simple list tool with one optional parameter and no output schema, the description is complete. It specifies returned fields and provides usage context for obtaining campaign_id.
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 input schema has 100% description coverage for the single parameter 'status', including its enum values and optional nature. The description does not add additional meaning beyond the schema, so baseline score of 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?
The description clearly states 'List your campaigns' with specific fields (ID, name, status, description, lead counts). It distinguishes from sibling tools like create_campaign by focusing on reading data and obtaining campaign_id for downstream operations.
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 explicitly says 'Use this to obtain campaign_id when adding leads, generating messages or approving drafts.' This provides clear context for when to use the tool, though it does not mention alternatives or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but there is some overlap among search tools (search_job_postings, search_google_xray, search_linkedin_people, search_web) and messaging tools (send_connection_request, send_linkedin_message, reply_to_chat). However, detailed descriptions clarify the differences.
All tools follow a consistent verb_noun snake_case pattern (e.g., add_contacts_to_campaign, list_campaigns). No mixing of conventions.
48 tools is high but justifiable given the broad domain (LinkedIn outreach, CRM, campaigns, job postings, etc.). However, some tools could be consolidated (e.g., multiple search tools).
The tool set covers the entire workflow: searching, connecting, messaging, campaign management, CRM operations (fields, stages, tasks, notes), job postings, and posting. No obvious gaps.
