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

Beyond the annotations, it discloses asynchronous execution, immediate return of a job id, the required polling workflow, and the result of repeating a call with the same key. These details explain the operational lifecycle and safe retry behavior rather than merely asserting idempotency.

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?

Three compact sentences front-load the operation and use case, then cover polling and retries. Every sentence contributes actionable information, with no filler or unnecessary enumeration of schema values.

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?

Together with the fully described input schema, annotations, and output schema, the description supplies what an agent needs to start an export and follow up on it correctly. Details such as export format or job duration are absent, but they are not necessary for selecting or initiating this straightforward four-parameter tool.

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 100%, and all four parameters already have clear descriptions, including the key's length and reuse semantics. The description usefully frames the optional fields as export filters and the key as a retry-safety mechanism, but adds little parameter meaning beyond the schema.

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 opening sentence specifies the operation and resource: starting an asynchronous export of filtered Vooks titles. The bulk-work contrast distinguishes it from title-search siblings, and naming get_export_job distinguishes export creation from job-status retrieval.

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?

It explicitly identifies bulk work that would otherwise require hundreds of searches as the use case and directs the agent to poll the returned id with get_export_job. It does not provide an explicit when-not rule or name search_titles or get_title for smaller lookups, so the selection guidance is strong but not exhaustive.

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