stop_list_export_tasks

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds only the HTTP method and a note about Python SDK parity, which doesn't disclose meaningful behavioral details beyond the annotations. No mention of response format, status values, or filtering behavior.

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 short phrase that front-loads the key information (HTTP method and resource). No wasted words or filler. It is concise, though arguably too minimal to be fully self-sufficient.

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?

With no output schema, the description should clarify what the tool returns, but it only states 'list of export tasks'. The status filter parameter is undocumented, and the overall behavior is under-specified. For a simple list endpoint, this may be enough for basic use, but it lacks detail needed for robust agent decision-making.

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 schema documents two optional parameters, but only dry_run has a description (50% coverage). The description does not explain the status enum values or the purpose of dry_run. Since the description fails to compensate for the undocumented status parameter, the parameter semantics remain incomplete.

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 identifies the tool as 'GET /api/v2/stop-list/export — список задач экспорта', which clearly indicates it lists export tasks. It distinguishes itself from sibling tools like stop_list_export_create, stop_list_export_download, and stop_list_export_delete. However, it doesn't elaborate on what an 'export task' is or how the list is structured.

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 provides no guidance on when to use this tool versus the many related sibling tools. No context about typical scenarios, prerequisites, or alternatives is given, leaving the agent to infer usage solely from the endpoint name and basic list semantics.

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