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

No annotations are provided, so the description carries the full burden, and it discloses almost nothing: no return shape, no pagination, no date-range defaults, no note that it is read-only. The only behavioral signal is the embedded method name getReportsByCampaign, implying a retrieval operation.

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 short fragment with no wasted words, but the brevity is under-specification rather than concision. Nothing is front-loaded because there is nothing substantive to front-load.

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?

For a five-parameter reporting tool with no annotations and no output schema, the description should explain what the report contains, how date ranges are interpreted, and what the caller gets back. None of that is present, leaving the agent guessing about return contents and default behavior.

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 100%, so all five parameters (adam_id, report_start_time, report_end_time, report_timezone, notification_message) are documented in the schema itself, making 3 the baseline. The description adds no additional meaning about date ranges or defaults, but the schema already does the heavy lifting.

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 is a noun phrase, "Campaign performance report (getReportsByCampaign)", that essentially restates the tool name rather than stating a verb and scope. The parenthetical API method name adds a small hint that this is a read/query operation, but an agent gets no statement of what is listed, in what granularity, or how it differs from the sibling list_ad_group_reports.

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?

There is no guidance on when to use this tool versus alternatives such as list_campaign_reports-adjacent siblings like list_ad_group_reports or list_campaigns, nor any prerequisites or exclusions. Usage must be inferred entirely from the name.

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