Yandex Metrika: status

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the description's real value-add is the auth disclosure — the tool functions before any Yandex sign-in, which annotations cannot express. Mentioning that it returns capabilities and a recommended next step also hints at the response shape without duplicating the output schema.

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 tight clauses with the purpose front-loaded and the workflow instruction immediately after. The middle list of returned items is slightly run-on but each element carries information; no filler sentences.

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?

An output schema exists, so return-value detail is not required, and the sole optional parameter is fully described in the schema. The description supplies the two things structured fields cannot — ordering and pre-auth availability — leaving little an agent needs that is missing for such a simple discovery tool.

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 optional connection_id is fully documented there, so the baseline applies. The parenthetical "(connection_id values)" usefully signals that the tool emits the IDs the parameter consumes, but it adds no new syntax or filtering semantics beyond the schema.

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 ("Shows Yandex Metrika connections") and enumerates what the response contains (state, export jobs, capabilities, next step). It is distinguishable from siblings like metrika_list_counters or metrika_get_job, though it does not explicitly name which sibling it replaces.

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?

"Call it first" gives an explicit ordering instruction that tells the agent where this fits in a workflow, and "works before any Yandex sign-in" clarifies the prerequisite state. It stops short of naming alternatives or stating when-not to use it, so no exclusion guidance is present.

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