mgmt_cloud_exports_list

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states 'List', implying a read operation, but does not explicitly confirm non-destructiveness, mention pagination, response format, or any authentication requirements. The description adds no behavioral context beyond the action itself.

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 core sentence is concise and to the point, but the leading URL is unnecessary noise that wastes the first position. Once past the URL, the description is efficient with no fluff. It is appropriately short for a simple list operation.

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?

The tool is simple (a list operation with two parameters, both documented), so a minimal description is acceptable. However, it lacks any mention of response structure, pagination, or prerequisites. Given the absence of annotations and output schema, a bit more context would improve completeness.

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%, so the schema already documents both parameters. The description's phrase 'for counter' merely reiterates the counterId parameter without adding new meaning. It provides no extra syntax or formatting details, so it meets the baseline for high schema coverage.

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 states a specific action ('List') and a clear resource ('Yandex Cloud export objects') scoped to a counter. It is unambiguous and distinct from siblings like mgmt_cloud_export_remove (which deletes) and other list tools. The leading URL is noise but does not confuse the purpose.

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 implies when to use it (when you need to list cloud exports for a counter), but provides no explicit guidance on when not to use it or alternatives. There are many list tools in the sibling set, and the description does not differentiate usage criteria or mention edge cases.

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