Список целей счётчика

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds transparency by mentioning the default counterId (YANDEX_METRIKA_COUNTER_ID) and that it uses the Management API, providing useful context without conflicting with annotations.

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 concise: it states the main purpose, the use case, and the default behavior in three short sentences. The parameter description is also brief and to the point. No unnecessary details or redundancy.

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 description provides enough context for an agent to understand when and why to call this tool: to fetch goal IDs for conversion metrics in get_statistics, with a default counterId. It does not detail the return structure, but given the simple listing nature and lack of output schema, this is acceptable. The mention of Management API adds relevant context.

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 parameter counterId is described in the schema, and the description reinforces its role and default. The description adds context about why the parameter matters (goal IDs for conversion metrics), but the core parameter semantics are already clear from the schema, so the added value is moderate.

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 tool's purpose: 'Возвращает цели (конверсии), настроенные на счётчике Метрики' (Returns goals configured on the Metrika counter). It also distinguishes itself from siblings by specifying it's for listing goals, not counters or statistics, and explains the relevance to get_statistics.

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 this tool: to obtain goal IDs needed for conversion metrics in get_statistics. It also notes the default counterId behavior. However, it does not explicitly contrast with sibling tools like list_counters, though the purpose is clear enough.

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