stop_list_export_create

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

Annotations already cover destructive/write behavior (destructiveHint=true, readOnlyHint=false), so the description's burden is lower. However, it adds no behavioral context beyond the endpoint; it doesn't explain side effects, task lifecycle, or authentication requirements.

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 concise sentence with no redundancy, making it efficient. However, it is somewhat under-specified, but for conciseness scoring it earns a 4.

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?

This is a creation tool with no output schema, so the description should explain what happens after the task is created or what response to expect. It lacks such context, making it incomplete for operational use.

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%, with the only parameter 'dry_run' already having a description. The tool description adds no additional parameter semantics, so the baseline 3 is appropriate.

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 action 'создать задачу экспорта' (create export task) and provides the endpoint. It distinguishes the tool as a creation operation, though it does not explicitly differentiate it from sibling export tools like stop_list_export_tasks or stop_list_export_download.

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?

No guidance is provided on when to use this tool versus alternatives, nor are any prerequisites or context for using it mentioned. The description simply states the action without usage instructions.

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