v4goals_get_retargeting_goals

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

With no annotations provided, the description carries the full burden. It only states 'Get' implying a read operation but does not disclose any side effects, authentication requirements, rate limits, or other behavioral traits. Basic purpose is clear but lacks depth.

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 with two sentences, but the second sentence requires the agent to invoke another tool for parameter details, which reduces efficiency. It is not optimally structured for self-contained usability.

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 is incomplete for a tool with one parameter, relying on tool_help for essential parameter information. While output schema exists, the lack of parameter details makes it insufficient for confident invocation.

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 input schema has 0% description coverage and the description offers no parameter guidance, simply redirecting to tool_help for parameters. The agent receives no information about the format or constraints of campaign_ids.

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 verb 'Get' and the resource 'retargeting goals for campaigns', and explicitly distinguishes from sibling v4goals_get_stat_goals by noting it's for Metrica stat goals.

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 provides an explicit alternative tool for a different use case (Metrica stat goals), guiding the agent when not to use this tool. However, it does not elaborate further on when to use this tool vs other siblings, though the alternative is sufficient for this context.

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