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

Annotations already declare it read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that by explaining what a pending_review hold means (no charge, nothing sent to the ad platform), which is not in the annotations.

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?

Front-loads the core purpose, follows with the diagnostic use case, and ends with the return shape in three tight blocks. Every sentence carries weight and nothing is redundant.

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?

With no output schema, the explicit return structure is a valuable addition, and the diagnostic framing plus pending_review semantics round out behavior. The only gap is that the input parameters are entirely undocumented, which is a real omission for a five-parameter tool.

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 description coverage is 0% and there are five parameters (ideaId, runId, limit, offset, response_format), yet the description explains none of them — not even which identifiers are required. It only describes the return shape, leaving every input undocumented.

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?

States a specific verb ('Get') and resource ('chronological event log for an Ad Run') and enumerates the event types it contains (provisioning steps, status changes, review holds, errors). An agent can distinguish the timeline-oriented purpose clearly, though it does not explicitly contrast itself with siblings like get_ad_run or list_ad_runs.

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?

Gives a concrete diagnostic use case ('why is my run not live yet?') that tells the agent when this tool is the right one. It does not, however, name an alternative tool or state when NOT to use this, so the routing is contextual rather than exhaustive.

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