list_landing_page_reports

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

Annotations already provide readOnlyHint=true, indicating a safe read operation. The description adds that the tool retrieves aggregate performance reports and returns JSON, with pagination support. While it doesn't disclose rate limits or performance implications, the combination of annotations and description gives sufficient behavioral insight.

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 short and front-loaded: a single sentence stating purpose, followed by a paragraph explaining parameters and return. Every sentence adds value, with no wasted words.

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?

Given the presence of an output schema, the return description is adequate. However, the description lacks explanation of the account parameter's behavior (e.g., default account when null). With 3 optional parameters and pagination described, the tool's complexity is moderate, but the missing parameter information leaves a gap in completeness.

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?

The description explains the 'count' and 'offset' parameters with defaults and purpose (pagination), but completely omits the 'account' parameter. Since schema description coverage is 0%, the description is expected to compensate but fails to describe one of three parameters, leaving its role ambiguous.

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 lists reports for all landing pages, using verbs like 'list' and 'retrieves' with the resource 'aggregate performance reports across every landing page'. This distinguishes it from sibling tools like list_landing_pages (which lists landing pages themselves) and get_landing_page_report (which likely gets a single report).

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?

The description provides pagination guidelines ('Use count and offset to page through large result sets') but does not explicitly state when to use this tool versus alternatives like get_landing_page_report for individual reports or list_landing_pages for landing pages. The context of listing all reports is implied but not contrasted with siblings.

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