mailchimp_landing_pages

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

With no annotations, the description carries the full burden of behavioral disclosure. It specifies what each action returns (status/URL, full record, rendered HTML), making the read-only nature evident. It does not discuss rate limits, authentication, or error conditions, but for a retrieval tool this is reasonably transparent.

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 at two sentences, front-loads the resource, and every clause provides necessary information. The action list is formatted clearly without redundancy. 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?

The description covers the main actions and their outputs, but does not explicitly state that details/content require a page_id or that list is needed first. The schema hints at this via 'from action=list,' yet the description could be more self-contained. Overall, it is mostly complete for a read-only resource 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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantics to the 'action' parameter by explaining what each enum value returns, which is not fully detailed in the schema. This elevates the score above baseline since the schema's action description points back to the tool description.

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 identifies the resource (landing pages) and enumerates three specific actions (list, details, content) with their return types. It clearly distinguishes from sibling tools by focusing on landing pages. However, it lacks a direct verb phrase like 'Retrieve landing pages,' making the primary purpose slightly indirect.

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 explains how to choose among actions ('Set action to one of: list...'), which is clear within the tool. However, it does not mention when to use this tool versus alternatives like mailchimp_search or mailchimp_campaigns, nor does it exclude any use cases. The guidance is implied rather than explicit.

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