List Recipes Bulk Actions Export

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' weakly signals a read-only retrieval, but the description reveals nothing about scope, pagination, authentication, response shape, or whether it returns metadata versus file content. It adds no meaningful behavioral context beyond the name.

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 three-word description is undeniably short, but this is under-specification rather than effective conciseness. Nothing useful is front-loaded, and every essential piece of context is omitted.

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?

Even though the input is simple and an output schema exists, the description still fails to explain what the operation returns, how it relates to export creation and download siblings, or when to invoke it. The absence of annotations makes this gap more severe.

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 tool has one optional parameter, accept-language, with no schema description coverage. The description does not mention this parameter, its effect, or acceptable values, so the agent receives no semantic guidance beyond the raw field name.

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 'Get Exported Data' states a generic action and object but not that this tool specifically lists recipe bulk-action exports. It does not distinguish the tool from create_recipes_bulk_actions_export or list_recipes_bulk_actions_export_by_export_download; the name and title carry the actual meaning.

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?

There is no guidance about when to call this tool, what conditions select it, or which sibling tools are alternatives. Given many related export endpoints in the sibling list, an agent cannot determine whether to choose this over list_recipes_exports or the download endpoint.

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