get_adset_details

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

No annotations are provided, so the description carries full burden. It discloses that access_token is optional and uses caching, but does not mention read-only nature, error handling, rate limits, or authentication requirements beyond the token. Adequate but not comprehensive.

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 and easy to read, with a clear header and structured Args section. The example, though slightly verbose, enhances usability without bloating the description.

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?

An output schema exists (implied), so return values don't need explanation. The description covers input parameters and basic usage. It lacks error conditions or edge cases but is sufficient for a simple read tool given the output schema is present.

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 adds value by explaining adset_id as 'Meta Ads ad set ID' and access_token as optional with caching behavior. However, the example usage suggests positional argument passing, which may conflict with the schema's named parameter convention.

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 it gets detailed information about a specific ad set, with a clear verb and resource. However, it lacks specifics on what details are provided and doesn't differentiate from sibling tools like get_ad_details or get_campaign_details.

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 includes an example of how to call the function and notes that access_token is optional with caching behavior. However, it does not explicitly state when to use this tool over alternatives (e.g., get_adsets for listing) or mention prerequisites or limitations.

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