Await Cloud Credentials

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

Annotations indicate openWorldHint, idempotentHint, and non-destructive. Description aligns by noting polling, timeout, and secure handling. It adds context beyond annotations: workflow prerequisite, credential handling, and subscription requirement. Could mention that the tool blocks until timeout or success, but the timeout parameter implies this.

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 sections, emoji, and bullets. Front-loaded with core purpose. Slightly verbose in the workflow explanation but every sentence is informative. Could be trimmed slightly, but still effective.

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?

Given 3 parameters, no output schema, and a blocking poller, the description covers trigger conditions, required session_id, optional parameters, workflow steps, and security note. Missing explicit return values (e.g., what happens on success/timeout), but the output schema is absent and the tool's behavior is implied.

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 coverage is 100% with parameter descriptions. The description reinforces the session_id format ('pass back EXACTLY... including the ?token=... suffix') and clarifies defaults and constraints for cloud and timeout. Adds value by explaining the suffix importance and the purpose of each parameter.

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 'Wait for the user to securely connect their cloud account and subscribe to Luther Systems.' It uses specific verbs ('await', 'polls') and identifies the resource ('cloud credentials'). The tool's purpose is distinct from siblings like tfdeploy or convoawait.

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 use: 'when tfdeploy returns an auth_required, no_credentials, or credentials_expired error.' Provides a step-by-step workflow and an important negative instruction: 'Do NOT call this tool without first showing the connect URL to the user.' This leaves no ambiguity.

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