sf_update_campaign

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

The description implies a write operation but lacks details on side effects, return values, permission requirements, or whether updates are partial or full replacements. With no annotations, the description carries the burden, and it fails to disclose these aspects.

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, efficient sentence that conveys the core purpose without unnecessary words. It is front-loaded and easy to parse.

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?

The tool modifies data but provides no information about output, error handling, confirmation, or required permissions. Given the absence of an output schema and the presence of nested parameters, the description is insufficiently complete for safe invocation.

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 with clear parameter descriptions. The tool description adds 'any fields', which is already implied by the 'fields' object. It does not provide additional formatting or allowed values beyond the schema.

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 action ('Update') and the resource ('any fields on an existing Salesforce campaign'). It effectively differentiates from sibling tools like sf_create_campaign or sf_get_campaign.

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 (e.g., sf_update_campaign_member_status, sf_update_contact). There are no prerequisites or context about when updates are appropriate.

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