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

Annotations already indicate this is a read-only, non-open-world operation. The description adds that it waits on a previously initiated sign-in, which is useful context, but it does not disclose what happens on timeout, whether it polls, or what result is returned after waiting.

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 a single short sentence with no filler and the key action is front-loaded. It is efficient, though extremely terse for a tool whose behavior depends on a prior operation.

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 read-only wait/polling tool with no output schema, the description gives the minimum context: it waits on a sign-in started elsewhere. It still omits important operational details such as timeout outcome, return values, and error behavior, which are left to inference.

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 67%, with 'org' and 'wait' documented in the schema. The description connects 'connectId' conceptually to a sign-in started by 'cloud.accounts.connect', but it does not add format, sourcing, or timeout semantics beyond what the schema already provides.

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 action ('Wait') and object ('a sign-in'), and it links the tool to the prior connect flow. It is distinguishable from the sibling 'cloud_accounts_connect', though it references that tool by an approximate dotted name rather than the sibling's actual name.

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 prerequisite is implied: this tool is used after a sign-in is started with 'cloud.accounts.connect'. However, it does not explicitly say when not to use it, what to do if no sign-in has been started, or how it relates to 'cloud_accounts_connect' versus other account tools.

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