Show recent audit log entries

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety behavior is covered without the description. The description adds genuine value by stating the log contains dry-run rehearsals as well as writes, but it omits ordering (newest first?), what happens when more entries exist than the limit, and any retention window.

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?

A single front-loaded sentence with the scoping detail in parentheses; nothing is wasted and the key noun phrase comes first. Appropriate size for a one-parameter read tool.

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, so return-value format need not be explained, and annotations cover the safety profile. Still, for a tool whose only knob is a truncation limit, the definition leaves limit behavior and sibling routing unexplained, which are the two things an agent most needs here.

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?

There is one parameter, 'limit', with a default of 20 and 0% schema description coverage, so the description carries the full burden of explaining it. The description never mentions 'limit' at all — no maximum, no statement about the default, and no clarification whether it truncates to the newest N entries. An agent must infer this entirely.

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?

Specific verb ('Show') plus a specific resource ('the most recent audit log entries'), with the added scope clarification that entries cover both writes and dry-run rehearsals. It does not differentiate itself from the sibling pinterest_ads_audit_lookup, so an agent cannot tell from the description alone which of the two audit tools to reach for.

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?

Usage is implied by 'most recent' (recency-oriented inspection), and the dry-run mention hints at a post-rehearsal verification use case. However, there is no explicit when-to-use statement and no guidance on when to prefer pinterest_ads_audit_lookup instead, which is the obvious alternative in the sibling list.

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