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

readOnlyHint=true already declares the safety profile, and the description goes further by disclosing the concrete return fields and, most usefully, that each date's _id is the event_date_id accepted by other tools. That cross-tool identity mapping is real behavioral context not present in annotations or schema.

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?

One dense sentence opens with the verb and payload list, then the hidden-resource hint, then the endpoint. Efficient and front-loaded; the REST path is mild redundancy but harmless.

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 carries the burden of describing returns and does so by enumerating the main fields, plus it explains the event_date_id linkage needed for follow-up calls. It stops short of noting region-scoping behavior of override_location, which is the only notable gap.

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 both event_id and override_location are already documented in the schema, making 3 the baseline. The description mentions dates and ids but never explains the override_location region semantics, adding nothing parameter-specific beyond the schema.

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?

States a specific verb ('Fetch') and resource ('one event'), then enumerates exactly what is returned. 'One event' clearly distinguishes it from the sibling list_events, and the REST path removes any ambiguity about the underlying resource.

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?

Usage is implied by the singular-resource framing, so an agent can infer it is for retrieving a known event_id rather than enumerating. However, it never says when to prefer this over humanitix_list_events or humanitix_get_order, nor are there any prerequisites or exclusions.

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