Get Event Details

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

No annotations are present, so the description bears the full burden. It only says 'get event by numeric ID or URL slug' and does not disclose behavior such as error handling for invalid IDs, return format, or any rate/latency considerations. This is minimal transparency for a retrieval tool.

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, front-loaded sentence that conveys the essential purpose without waste. It is appropriately concise for a simple 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?

With no annotations, no output schema, and an empty input schema, the description should compensate by explaining expected return values, error behavior, or relationship to sibling tools. It does none of this, leaving significant gaps for an agent trying to invoke it correctly.

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 input schema is empty (0 properties), yet the description references numeric ID and URL slug as inputs. This creates a mismatch: the description adds meaning by naming identifier types, but it does not specify parameter names, locations, or formats, making correct invocation unclear. Baseline for 0 params would be 4, but the implied parameters and missing schema reduce it.

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 'Get event by numeric ID or URL slug' clearly states the action (get) and the resource (event), and specifies how the event is identified. It distinguishes from list-type siblings like list_events, but does not explicitly differentiate from get_event_metadata, so it isn't a perfect 5.

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 about when to use this tool versus alternatives like get_event_metadata or list_events. There is no mention of preferred usage, exclusions, or fallback tools.

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