Wait for source processing

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

The description adds polling, timeout, and failure behavior beyond the annotations (readOnlyHint, openWorldHint). It discloses the read-only polling nature and the failure condition (TimeoutError), which the annotations do not specify.

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 efficient sentence with no wasted words. However, it could be slightly improved by structuring into use context and behavior, but it remains appropriate for a simple polling tool.

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 the tool's simplicity and complete schema annotations, the description covers core behavior but omits details like polling interval, retry logic, or what READY status entails. Adequate but not fully comprehensive.

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%, so the description adds minimal value beyond what the schema already provides. The mention of 'configured timeout' aligns with timeoutSeconds but does not enhance parameter understanding.

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 tool polls until the source reaches READY status, with a timeout on failure. This specific verb+resource combination distinguishes it from sibling tools like source_list or source_refresh.

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 implies usage when one needs to wait for a source to be ready, but lacks explicit guidance on when to use this versus alternatives like source_list or source_refresh. No when-not-to-use scenarios are provided.

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