Wait for export

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

Annotations already mark it read-only and closed-world. The description adds that the call blocks until completion and returns file paths, which is useful context; however, it omits timeout/failure behavior and whether it starts a new export if none is active.

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?

One compact sentence with the action and return value front-loaded. No wasted wording or redundant restatement.

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 wait tool with annotations and no output schema, it covers the core blocking behavior and return value. It is less complete because the timeout parameter's semantics and failure mode are left undocumented.

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 only parameter, timeoutSeconds, is never mentioned in the description, and schema description coverage is 0%. The description does not explain units, default behavior, or what happens when the timeout expires, so it adds no meaning beyond the schema's field name and constraints.

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 ('Waits') and resource ('export'), and clarifies it targets the current or next export and returns file paths. It does not explicitly contrast with export_file or other siblings, so it is clear but lacks explicit sibling differentiation.

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?

Implies use after an export has been started ('current or next export'), but does not explicitly say when to call it versus export_file, or whether it should be used only when an export is already running. No exclusions or alternatives are stated.

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