get_sponsored_ads_report

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

The description notes it's a read operation ('[Ads / read]') and warns that it's an introspection stub on local stdio. However, without annotations, it should disclose more about data recency, pagination, or rate limits.

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?

Two concise sentences that cover purpose and a critical limitation. No wasted words, though the second sentence could be phrased more clearly.

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 provides enough context for a basic understanding but lacks details on output format or what 'retained report views' entails. Given the complexity (7 parameters, no output schema), more detail would be beneficial.

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 coverage is 100%, so parameters are already well-documented. The description adds no additional semantics beyond the schema fields.

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 clearly states it's for reading consolidated SP/SB/SD sponsored ads reports. It distinguishes from sibling tools by specifying 'Consolidated' and 'retained report views', though it could be more explicit about the exact data.

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?

No guidance on when to use this tool vs alternatives like get_sponsored_ads_entities_live or get_campaign_performance. The note about 'hosted endpoint only' is important but does not provide comparative usage advice.

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