get_landing_page_report

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description reinforces this by stating 'Read-only, safe to retry.' It adds behavioral context about authentication and concurrency limits. No contradiction with 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 well-structured: a one-line title, a short paragraph on purpose, usage guidelines, and then parameter descriptions in a clean list format. It is appropriately sized and front-loaded with essential information.

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 read-only tool with two parameters and an existing output schema, the description covers purpose, parameters, behavioral notes, and return format. It does not list output fields but that is expected from the output schema. The concurrency limit adds value. Minor gap: could mention potential errors, but overall complete.

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 0%, so the description must compensate. It explains outreach_id as the identifier for the landing page to report on, and the account parameter with an example and reference to list_accounts. This adds significant meaning beyond the schema's bare type definitions.

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 the tool retrieves a detailed performance report for a single landing page, distinguishing it from sibling tool get_landing_page. It specifies the resource (landing page report) and the action (get report), and mentions the key identifier (outreach_id).

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 explicit usage context: 'Use this to review visits, conversions, and other metrics for a specific page.' It also notes authentication via API key and a concurrency limit of 10. However, it does not explicitly name alternative tools or state when not to use it, but the context is clear given siblings like list_landing_page_reports.

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