get_event

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

Since no annotations are provided, the description must bear the full burden. It only describes the *content* of the response (the event and GenAI description) but offers zero insight into the operational behavior (e.g., latency, status codes, or data format).

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 extremely short and highly efficient. Both parts of the sentence directly contribute to defining the tool's scope and output characteristics.

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?

The description is insufficient for a data retrieval tool without an output schema. 'In detail' is too abstract, leaving the AI agent uncertain about the structure or nature of the detailed information being returned.

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?

With only one parameter (event_id) and zero schema coverage, the description doesn't add substantial meaning about the nature of the parameter itself beyond what the schema defines. This meets the minimum viable standard for a single-parameter tool.

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 clearly states the function is to retrieve 'One event in detail.' It sufficiently differentiates itself from siblings like list_events by specifying the singular nature of the retrieval.

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?

The description provides implied guidance by highlighting that it includes the GenAI description when available. However, it does not give explicit instructions on when *not* to use it, such as when only basic metadata is needed.

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