get_landing_page_report

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

Annotations indicate readOnlyHint=true, so the description adds value by specifying the report contains visits, conversions, and metrics. While the return format is vaguely described as 'JSON with the landing page report', it provides sufficient behavioral context beyond 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 concise and front-loaded with the purpose. The Args section is redundant with the schema but useful given the schema lacks descriptions. Overall, it earns its place without being verbose.

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 includes return content (visits, conversions, etc.) and distinguishes from similar tools. While it does not mention error handling or pagination, the output schema exists to fill in structural details, making it fairly complete for a simple retrieval tool.

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 for all parameters. It only documents outreach_id in the Args section, omitting the optional account parameter entirely. This leaves the agent uninformed about when to provide an account, which is a significant gap.

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 retrieves a detailed performance report for a single landing page using an outreach id. It distinguishes from siblings like get_landing_page (page details) and list_landing_page_reports (list of reports), ensuring no ambiguity.

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 advises using this tool to review visits, conversions, and other metrics for a specific page, which guides its use. However, it does not explicitly mention when not to use it or direct to alternatives like list_landing_page_reports for multiple pages.

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