sf_list_campaigns

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

The description implies a read operation ('list') and mentions optional filters, but no annotations are provided. It does not disclose pagination, rate limits, or exactly what data is returned. Transparent enough for a simple list but lacks depth.

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?

Single sentence, front-loaded, no redundant words. Efficiently conveys purpose and key filters.

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?

No output schema or annotations. Missing details on return fields, pagination behavior, and error handling. For a list tool with many siblings, more context is needed to help agent choose correctly.

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 50% (type and status have descriptions). The description only lists filter names without adding meaning beyond param names (e.g., does not specify defaults, min/max for limit, or accepted values for status/type).

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 tool lists Salesforce campaigns with optional filters, using the verb 'list' and resource 'campaigns'. It distinguishes from sibling 'sf_get_campaign' (single campaign) but not from other list tools like 'sf_list_objects'.

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 on when to use this tool vs alternatives, such as whether to use it for campaign summary vs. detailed member lists. No exclusions or recommended scenarios.

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