mailchimp_promos

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 does not state that the tool is read-only, nor does it describe error behavior, rate limits, or what happens when required IDs are missing. The only behavioral hint is the action names implying retrieval, but this is not explicit.

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 two sentences long: a clear summary followed by a compact enumeration of the four actions and their parameter needs. No filler or redundant content; every word earns its place.

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 tool with six parameters and no output schema, the description covers the action-to-parameter mapping but omits return value shapes, pagination behavior (though count/offset are in schema), and examples. It is adequate for a moderately complex read-only tool but not comprehensive.

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 schema already provides 100% parameter descriptions, so the baseline is 3. The description adds value by mapping actions to required parameters and showing dependencies (e.g., action='code' needs both promo_rule_id and promo_code_id), which is not present in the schema alone.

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 identifies the resource (promotion rules and promo codes) and the scope (one store), and the action enum explicitly defines what can be retrieved. This distinguishes it from all sibling tools like mailchimp_products or mailchimp_orders, which cover different resources.

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 gives clear usage instructions for each action, telling the agent which parameters are needed (e.g., 'rule (one rule, needs promo_rule_id)'). It does not explicitly mention alternatives or when not to use the tool, but since no other sibling handles promotions, the usage context is clear.

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