yd_smart_targets_get

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action is retrieval, without mentioning side effects, permissions, rate limits, pagination, or constraints on input combinations. This is minimal transparency.

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 a single sentence, which is concise but under-specified. It could include more detail about parameter interaction or return results without becoming verbose. It is not structured with headings or examples.

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?

Given the tool has 4 parameters and no output schema, the description is too brief. It does not explain how parameters combine, that all are optional, or what the response contains. For a get operation, information about default behavior or limits would be helpful.

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 low (25%), with only 'client_login' having a description. The description mentions the three ID parameters by their types (campaign, ad group, target IDs) but does not explain their optionality, format, or behavior when multiple are provided. It adds little meaning beyond the parameter names.

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 action 'Get' and the resource 'smart ad targets', with filtering by campaign, ad group, or target IDs. It distinguishes the tool from siblings like 'yd_smart_targets_add' and 'yd_smart_targets_action'.

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?

No explicit guidance on when to use this tool versus alternatives. The description only implies retrieval via the word 'Get', but lacks context on when to choose this over other smart target operations or other tools.

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