salesforce_backup

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

With no annotations provided, the description carries full burden and discloses key behavioral traits: it's an asynchronous operation ('Runs asynchronously in background'), returns immediately with a job ID, and requires follow-up with another tool. However, it doesn't mention potential side effects like API usage impact or resource consumption.

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 tightly focused sentences with zero waste: first states purpose, second explains execution behavior, third provides usage guidance. Every sentence earns its place and information is front-loaded appropriately.

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 complex backup tool with 8 parameters and no output schema, the description provides good context about the asynchronous nature and workflow. However, it doesn't mention what the job ID looks like or potential error conditions, leaving some gaps for the agent to infer.

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 100%, so the schema fully documents all 8 parameters. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score for high coverage.

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 specific action ('Start comprehensive backups'), resource ('Salesforce data including all file attachments'), and scope ('comprehensive'). It distinguishes from siblings like 'salesforce_backup_status' by indicating this initiates the backup while status checks progress.

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?

Explicitly states when to use this tool ('Start comprehensive backups') versus alternatives ('Check progress with salesforce_backup_status'), providing clear guidance on the asynchronous workflow and sibling tool relationships.

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