list_lead_campaigns

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

Without annotations, the description has the full burden. It only says 'list' and 'status', but does not disclose whether it is read-only, any authentication needs, rate limits, or that it lists only recent campaigns (presumably not all).

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?

The description is a single sentence that conveys the essential purpose without any fluff. Every word 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?

Given the simplicity (no parameters, no output schema), the description is adequate but not complete. It does not clarify what 'recent' means or provide any details about the output structure beyond 'status'.

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?

There are no parameters, and schema coverage is 100% (trivially). According to guidelines, zero parameters baseline is 4, and the description adds no parameter-specific meaning but fulfills the purpose.

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 the verb 'list' and the resource 'lead scraping campaigns', and mentions the output includes 'status'. It distinguishes from sibling tools like 'scrape_leads' (creating) and 'export_leads' (exporting), but the term 'recent' is somewhat vague.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_leads' or 'scrape_leads'. There are no explicit conditions or exclusions for usage.

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