Raw Reddit report

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context beyond that: breakdown constraints, date-locality semantics, filter expression examples, and microcurrency conversion. It does not contradict 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?

The description is compact and front-loaded, using labeled parameter notes and examples without fluff. The structure is generally clear, though some behavioral details like 'Dates are account-local days' are tucked inside the breakdowns explanation rather than given their own parameter entry.

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?

The description covers the core purpose, differentiation, and main parameter constraints, but with 7 parameters and no schema descriptions it leaves gaps around defaults and timezone/account semantics. The presence of an output schema reduces the need to describe return values, but report behavior such as date requirements is still under-specified.

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 0% schema description coverage, the description must compensate, and it does explain fields, breakdowns, and filter with examples and constraints. However, it leaves ad_account_id, time_zone_id, date_range_start, and date_range_end without dedicated explanation, making the parameter documentation incomplete.

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 and resource: 'Run a custom Reddit Ads report'. The phrase 'for metrics get_reddit_performance omits' clearly distinguishes this tool from the sibling get_reddit_performance, so an agent can tell what it is 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?

Explicitly positions the tool as the choice for metrics get_reddit_performance omits, which gives a clear selection condition against the most relevant sibling. It does not cover other possible alternatives like get_reddit_campaigns or get_reddit_ads, but the main routing decision is addressed.

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