Reddit account change history

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

Annotations only declare readOnlyHint and destructiveHint. The description adds meaningful behavioral context: the 30-day account-local default window, child-entity inclusion, AdLoop user attribution behavior, and money fields in account currency. No contradiction with 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?

The description is five compact sentences with the core purpose front-loaded. Every sentence adds a distinct fact: purpose, trigger, window, filtering, attribution, and currency. There is no filler or repetition of schema defaults.

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 an output schema and safety annotations already present, the description covers purpose, usage trigger, defaults, filter semantics, and currency. Minor gaps remain around ad_account_id semantics, date format, and limit behavior, but the overall context is strong enough for an agent to call the tool effectively.

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%, so the description must compensate. It does clarify entity_type allowed values, entity_ids behavior, and the default date window. However, it leaves limit, ad_account_id, and date_range_start/end formats unexplained, so it only partially compensates for the missing schema descriptions.

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 opens with 'Who changed what in the Reddit ad account: field, before/after, member, time,' which precisely names the resource and the data shape. It clearly distinguishes this history tool from sibling tools like get_reddit_performance or get_reddit_campaigns by framing it as a change-audit tool.

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?

It gives an explicit trigger: 'The first thing to check when performance moves.' It also explains when to use the optional entity filtering and that child entities are included. It does not explicitly name alternatives, but the usage context is clear enough that an agent can decide when to invoke it.

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