Reconnect an account

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

Annotations already indicate mutation (readOnlyHint=false), idempotency, and non-destructiveness. The description adds a concrete behavioral detail beyond annotations: it 'produces a fresh QR code' when the existing link is invalid. This is useful context without contradicting the annotation profile.

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 two concise sentences. It front-loads the core action ('Restart the account's session') and then gives the trigger and outcome. Every phrase earns its place with no redundant filler.

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 one-parameter tool with no output schema, the description provides the essential trigger ('disconnected'), the behavior ('restart session'), and the produced outcome ('fresh QR code'). It could go slightly further by explaining the output format or side effects, but nothing critical is missing for correct selection and 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 is fully documented with 100% coverage, including the meaning of accountId: 'The wuapi account id of the linked number to act as (from list_accounts).' The description adds no parameter-specific insight, but the baseline of 3 is appropriate given complete schema 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 states a specific verb and resource: 'Restart the account's session.' It further clarifies the concrete outcome by saying it 'produces a fresh QR code' when the link is no longer valid, which distinguishes it from related tools like get_account_qr_code.

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 provides an explicit trigger condition: 'Use it when an account is `disconnected`' and 'when the link is no longer valid.' However, it does not explicitly name alternatives or state when not to use it, so it falls short of fully routing the agent away from sibling tools.

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