get_adset_details

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. It describes the tool as a read operation and lists the type of information returned, but does not address potential side effects, authorization needs, error conditions, rate limits, or the structure of the response. The behavioral transparency is minimal.

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 extremely concise: two sentences plus an args line. The main purpose is front-loaded, and there is no superfluous information. Every word serves a clear function, making it efficient for an agent to parse.

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's simplicity (single parameter, no output schema), the description provides a reasonable outline of what is returned (targeting, optimization, learning stage, etc.). It adequately differentiates from sibling tools. However, it lacks details on error handling, response format, or edge cases, which would enhance completeness.

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 parameter 'adset_id' is described as 'Ad set ID (numeric string)', adding semantic value beyond the schema which only specifies type string. The schema coverage is 0%, so the description compensates by clarifying the format. However, it does not explain the meaning or context of the adset ID, which is already implied by the tool name.

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 starts with 'Get detailed ad set information', clearly stating the verb (get) and resource (ad set details). It lists specific categories included, distinguishing it from sibling tools like get_adsets (which lists adsets) and get_ad_details (which gets ad details). The purpose is explicit and unambiguous.

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 offers no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or situations where other tools might be more appropriate. The only implied usage is when one needs detailed ad set info, but no explicit when/when-not or alternatives are given.

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