get_adset_insights

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

With no annotations, the description carries full responsibility for behavioral disclosure, yet it only restates the basic purpose. It does not mention output format, data scope, permission requirements, rate limits, or any side effects, offering no value beyond the tool name.

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, well-structured sentence that is concise and front-loaded with the core purpose. While it is minimal, it does not waste words and is appropriately sized for a simple read operation, though it could benefit from a bit more detail.

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?

This tool has 8 parameters, no output schema, and no annotations, making it fairly complex. The description only states the basic action and does not explain what 'performance insights' includes, how to construct time ranges, or what the response will look like, leaving significant gaps for the agent.

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 schema provides thorough descriptions for all 8 parameters, including default fields and valid date presets, giving 100% coverage. The description adds no additional meaning to the parameters, landing at the baseline score for strong schema coverage.

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 tool retrieves performance insights for a specific ad set, using the verb 'get' and the resource 'ad set'. It is clear what the tool does, but it does not explicitly differentiate from sibling tools like get_campaign_insights or get_ad_insights, though the name and 'specific ad set' provide some distinction.

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 no guidance on when to use this tool versus alternatives such as get_campaign_insights or get_ad_insights. It does not mention excluded use cases or recommend other tools for different aggregation levels, leaving the agent to infer usage solely from the name.

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