v4goals_get_stat_goals

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. The description mentions 'v4 Live' but does not clarify whether the tool is read-only, destructive, or side effects. It lacks details on permissions, data freshness, or response behavior.

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 brief (two sentences) and front-loads the purpose, but the second sentence defers parameter information to an external help tool, which reduces conciseness effectiveness. It could be more informative without being verbose.

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 tool has one required parameter with no schema coverage, and the description provides no input guidance. Although an output schema exists, the lack of behavioral transparency and parameter documentation makes the description incomplete for effective use.

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 0% and the description does not explain the campaign_ids parameter. Instead, it defers to tool_help for parameter details, adding no semantic value. The parameter's format, allowed values, and meaning are left entirely unspecified.

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 'Get Yandex Metrica stat goals available for campaigns (v4 Live)', providing a specific verb and resource. It also distinguishes from the sibling tool v4goals_get_retargeting_goals by noting the difference in goal type.

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 explicitly directs users to use v4goals_get_retargeting_goals for retargeting goals, offering clear guidance on when to choose an alternative. However, it does not specify when not to use this tool beyond that, and suggests calling tool_help for parameters, which is somewhat unusual.

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