Retrieve events within a specified date range. Provide start and end dates to view scheduled activities for food service operations.
List events in a date range.
| Name | Required | Description | Default |
|---|---|---|---|
| endDate | Yes | End, e.g. 2023-12-31T23:59:59 | |
| startDate | Yes | Start, e.g. 2023-01-03T09:00:00 |
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world nature are covered. The description adds only the date-range scoping, which is already implied by the required params. No mention of pagination, sort order, result size, or what happens with large ranges.
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?
A single tight sentence with no filler, front-loaded with the verb and resource. Appropriately sized for a trivial two-param list tool.
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 list tool without an output schema, the description gives no sense of return shape, volume, ordering, or pagination. It is minimally functional but incomplete relative to what an agent needs to call it confidently.
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% and both parameters already carry format examples, so the schema does the heavy lifting. The description adds nothing beyond restating the date-range filter. Baseline 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?
Clear verb 'List' plus resource 'events' with a scoping constraint (date range). It doesn't differentiate itself from any sibling, but none of the listed siblings cover events listing (only get_event for single retrieval), so the purpose is unambiguous.
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 indication of when to use this versus get_event, nor what to do after listing. No exclusions or prerequisites are stated. Only the most rudimentary implied usage from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.