metrika_logs_download_part

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds genuinely new output behavior: the row cap (max_rows <=1000) and the truncated=true signal when more rows exist. "Read-only" merely repeats the annotation, but the truncation contract is real value beyond structured fields.

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?

Two dense sentences plus a trailing "Read-only." The key information (what it previews, the row cap, truncation behavior) is front-loaded with no wasted words. Slightly hurt by the redundant read-only clause.

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 4-param tool with an output schema, the description sufficiently covers the output contract and row limits, so return values needn't be explained. But the two required identifying parameters (counter_id, request_id) remain undefined, leaving a real gap.

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?

With 0% schema description coverage across 4 parameters, the description carries the full burden. It adds a real bound for max_rows (<=1000) and hints at part_number via "one processed Logs API part", but counter_id and request_id go entirely unexplained in both schema and description.

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 (preview/download) and resource (one processed Logs API part) with the returned shape (columns + rows). It distinguishes itself from full exports, though it never names the closest siblings like metrika_logs_get or metrika_logs_list, so an agent gets the purpose but not the precise sibling routing.

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?

"For full exports download outside chat" implies this tool is for in-chat previewing rather than full retrieval, which is useful context. However there is no explicit when-to-use guidance against metrika_logs_get/list/evaluate, leaving the choice among the logs family to inference.

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