get_marketing_events

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, but it only states 'Fetch marketing events' which implies a read without detailing pagination, filtering, sort options, or return format. The schema hints at such capabilities, but the description fails to disclose them.

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 a single concise sentence with no fluff, effectively stating the core action. While it could include more detail, the structure is clean and front-loaded, earning a 4 rather than 5 due to missing useful context.

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 moderate complexity (5 parameters, no output schema, no annotations), the description is too thin. It neither explains what marketing events are, how to paginate, nor what the response contains, leaving the agent under-informed for correct invocation.

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 description coverage is 100%, with all five parameters clearly described in the input schema. The description adds no parameter information, but the schema already fully documents them, so the baseline score of 3 is appropriate.

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 'Fetch marketing events for the store' clearly indicates a read operation for a plural resource, distinguishing it from the singular get_marketing_event sibling. However, it doesn't explicitly say 'list' or clarify that it returns multiple events, leaving slight ambiguity about whether it fetches a single event or many.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention that get_marketing_event should be used for a single event, nor does it indicate any prerequisites or comparisons with create/update/delete marketing event tools.

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