Get Ad Account Activity Log

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

The description is consistent with annotations (readOnlyHint=true, destructiveHint=false) by using 'gets,' but it does not add behavioral details beyond what annotations convey. It lacks information about response format, pagination, or permission requirements, but the annotations already cover the safety profile adequately.

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: one sentence followed by a list of parameters. Every sentence is useful, and it is front-loaded with the main action. No extraneous content.

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 five parameters and lack of output schema, the description is thin. It does not explain what the activity log contains, how to interpret it, or any critical context like permission requirements. With many sibling tools, more detail would help the agent select appropriately.

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?

With only 20% schema description coverage, the description adds moderate value by clarifying the date format for 'since' and 'until' and stating defaults. However, it omits the 'response_format' parameter (which has a schema description) and provides only minimal info for others, partially compensating for the low 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 'Gets the activity/change log for an ad account,' specifying the verb, resource, and scope. It distinguishes itself from sibling tools that retrieve other types of ad account data, such as meta_get_ad_account or meta_get_ad_insights.

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. It does not mention when not to use it, prerequisites, or provide context for selecting this tool over other log or audit tools among the many siblings.

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