get_landing_page

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

Discloses read-only nature, safe to retry, max 10 concurrent requests, and 404 error for invalid page_id. With no annotations, the description carries full burden and performs excellently.

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, front-loaded with purpose, then usage, then behavior. Every sentence adds value with no redundancy.

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?

Covers purpose, usage, behavior, parameter details, and return fields (including JSON structure). Despite missing annotations, the description is comprehensive and requires no additional context.

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 single parameter 'page_id' is described as an alphanumeric string obtained from list_landing_pages. Schema coverage is 0%, but the description fully compensates by providing meaning and source.

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 full details of a landing page, including description and tracking settings. It distinguishes from sibling 'list_landing_pages' by emphasizing it's for retrieving details of a single page.

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?

Explicitly tells the agent to use 'list_landing_pages' to browse pages and discover page IDs, providing clear when-to-use guidance. Also mentions authentication and retry safety.

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