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

Annotations only flag it as non-readonly, open-world, non-idempotent. The description goes well beyond that, enumerating the three possible statuses, explaining that a link is returned for awaiting_approval but not for use_client_sign_in, that accounts are created on first sign-in, and that repeated calls while pending are improper. This is rich behavioral context an agent could not infer from annotations.

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?

Front-loaded with the core action and then structured by status branch, which is the right shape. It is somewhat long and repeats the 'ask them to...' instruction pattern, but nearly every sentence carries an actionable distinction (link vs no link, don't recall while waiting).

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 an OAuth-style connect flow with an output schema covering status, the description supplies everything an agent needs: trigger conditions, per-status handling, and the constraint against premature re-invocation. Return-value mechanics are correctly left to the 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?

The tool takes no parameters, so there is no parameter semantics to document; the description correctly avoids inventing any. Per the zero-parameter baseline this caps at 4 rather than 5, since there is no schema content for the description to enrich.

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?

States a specific verb and resource ('Connect this conversation to the person's Dreambooth Studio account') and the scope of the action. It is clearly distinguishable from siblings like connection_status or check_generation, which merely report state.

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 call: 'Call this when another tool reports that no account is connected, or when someone asks to connect or switch accounts.' It also gives a when-not-to-act rule ('do not call this tool again while waiting'), which is unusually strong guidance.

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