metrika_list_offline_conversion_uploads

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

'Read-only' merely restates readOnlyHint=true and adds nothing the annotations do not already declare. The parenthetical field list is the only extra behavior surfaced, and with an output schema present even that is largely redundant. No pagination, ordering, or scope behavior is disclosed.

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?

A single, front-loaded sentence with the main verb and resource leading and no filler. Every clause maps to tool behavior, and the read-only marker is placed last where it belongs.

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?

For a read-only list tool backed by annotations and an output schema, the description covers the core purpose adequately. It falls short on pagination semantics, filtering behavior for conversion_type, and any routing against sibling metrika tools.

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 0%, so the description must carry the parameter burden. It alludes to the counter (counter_id) and to a 'type' (conversion_type) but says nothing about limit/offset pagination or valid conversion_type values, leaving half the parameters undocumented anywhere.

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?

States a specific verb and resource ('List offline conversion uploads of a counter') and even names the returned item shape (id, status, line counts, type). It is clearly distinguishable from metrika_get_offline_conversion_upload (singular) and metrika_upload_offline_conversions, but it never explicitly names those siblings or draws the boundary.

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 when-to-use, when-not-to-use, or alternative guidance. 'Read-only' hints at the safe-read context but that is already carried by annotations, and nothing routes the agent between this tool and metrika_get_offline_conversion_upload or metrika_validate_offline_conversions.

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