list_landing_pages

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

No annotations provided, so description carries full burden. It discloses read-only nature, safe to retry, max 10 concurrent requests, and authentication via API key. Also explains pagination with offset.

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?

Highly concise: first sentence defines purpose, then clarifies domain, gives usage notes, and finally details parameters and return structure. No unnecessary 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 tool's simplicity (2 optional parameters) and presence of output schema, the description explains all relevant aspects: purpose, usage, parameters, and return format. It is self-contained and 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?

Input schema has two parameters with defaults but no descriptions. The description adds detailed semantics: count (1-1000, default 20) and offset (pagination, use when total_items exceeds count). This fully compensates for zero schema description coverage.

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 lists landing pages with specific fields (publication status, URLs, audiences). It distinguishes from get_landing_page (for full details) and list_campaigns (for email campaigns), using a specific verb and resource.

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?

Explicit instructions on when to use (list landing pages) and when not to use (for email campaigns, use list_campaigns; for full details, use get_landing_page). Also provides authentication, rate limit, and safety notes.

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