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

Annotations already indicate this is a non-read-only, idempotent, non-destructive operation. The description adds meaningful behavioral context: what ownership implies financially, the linked-workspace constraint, the locked-workspace restriction, and the relevant error case. This goes beyond the annotations without contradicting them.

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 sentences with no filler. The core action is front-loaded, the clarifying definition of 'owns' is useful, and the preconditions plus read-current-state pointer are each valuable.

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 simple two-parameter, idempotent setter with no output schema, the description is complete: it defines the operation, explains the ownership semantics, states the key constraints and error condition, and tells the agent how to inspect the current owner. Nothing essential is missing.

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 0%, so the description carries the burden. It effectively identifies linkedinAccountId as the LinkedIn account whose owner is being changed and workspaceId as the new target workspace, while adding constraints on workspaceId (must be linked, must not be locked). The parameter names are simple and the prose maps them clearly, though it does not use the exact field names.

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 operation: setting which workspace owns a LinkedIn account, and defines 'owns' concretely as paying for maintenance watchers and inbox messages. This distinguishes it from sibling tools like campaignstack_set_account_watcher by emphasizing the billing/ownership role.

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?

The description gives clear preconditions: the target workspace must be linked to the account and must not be locked, with an explicit error condition (ACCOUNT_OWNER_NOT_LINKED). It also directs the agent to campaignstack_get_account to read the current owner. It does not explicitly name alternatives or state when not to use the tool, but the context is clear.

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