humanitix_list_event_dates

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

No annotations are provided, so the description carries the behavioral burden. It discloses the return shape ('projection of each date with its id, name, and start/end times') and read-only framing via 'List', but says nothing about pagination, permissions, account-location scoping, or error behavior for an unknown event_id.

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?

Three short sentences, front-loaded with the action and object, with the dependency note and return summary following. No filler or redundancy.

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?

With no output schema, the description usefully specifies the returned projection so the agent knows what fields to expect. It is adequate for a simple three-parameter list tool, though it omits pagination and empty-result behavior.

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%, so all three parameters (including raw and override_location) are already documented in the schema. The description adds no syntax or constraint detail beyond implying the default projection, so baseline 3 applies.

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?

Specific verb (List) plus resource (event dates/sessions) scoped to a Humanitix event, and the parenthetical clarifies the domain term 'sessions'. An agent can distinguish this from humanitix_list_events and humanitix_get_event immediately.

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?

States why the tool matters: event dates are 'required identifiers for orders, tickets, and check-in tools,' which implicitly routes the agent here before calling order/ticket/check-in tools. It does not, however, explicitly say when to use this over humanitix_get_event or what to do if no dates exist.

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