yandex_metrica_get_counter

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the useful behavioral detail that this returns a configuration snapshot (settings, status, owner, timezone, site) rather than time-series data. It does not mention auth requirements or error behavior for a missing counter, so it stops short of a 5.

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 sentences, zero filler, with the purpose and returned fields front-loaded before the routing exclusion. Every clause earns its place.

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 single-parameter read tool with no output schema, the description compensates by naming what the response contains and by routing ambiguous discovery requests to the correct sibling. Nothing an agent needs to call this correctly is missing.

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 coverage is 100% and the single counter_id param is documented in-schema as the Yandex Metrica counter (tag) ID. The description only restates 'by id' without adding format, range, or resolution guidance. Baseline 3 is correct when the schema carries the parameter detail.

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 ('Get one Yandex Metrica counter by id') and enumerates the returned surface (settings, status, owner, timezone, site). It is immediately distinguishable from the sibling list_counters, which serves a different lookup mode.

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?

Gives an explicit use condition ('when the user already has a counter id and wants that counter's configuration'), an explicit exclusion ('Do not use this to discover unknown ids'), and names the alternative tool (yandex_metrica_list_counters) to use instead. Nothing is left to inference.

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