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

No annotations provided, so description carries full burden. Discloses deployment behavior, error handling steps, and return value including login URL. Could mention potential side effects like modifying org.

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?

Well-structured with bullet-point rules and explicit Args/Returns sections. Concisely communicates key information, though the two identical 'Deployment failed' returns are slightly redundant.

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?

Adequately covers prerequisite, user interaction, failure scenarios, and return format. Lacks details on agent_metadata structure, but overall sufficient for a deployment tool without output schema.

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?

Only one parameter (agent_metadata) with no schema description (0% coverage). Description adds basic meaning as 'agent metadata to deploy as a dictionary' but lacks structure details or examples typical for a nested object.

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?

Description clearly states 'Deploy a previously generated agent to Salesforce.' It uses a specific verb (deploy) and resource (agent), and distinguishes from sibling tools: generate_agent_metadata creates metadata, get_agent_requirements retrieves requirements.

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?

Describes when to use (after generate_agent_metadata) and instructs to always ask user first. Provides handling for failure cases. Lacks explicit when not to use but covers key usage context.

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