gamma_get_event_by_slug

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

Discloses that it returns full event-level context including nested markets, and clarifies that the slug is the URL path part not full URL. With no annotations, this is sufficient for a read operation, though additional details like error handling or return format could be added.

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 about six sentences, each serving a purpose: purpose, usage guidance, additional clarifications. No redundant or excessive text.

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?

Given the tool has one parameter and an output schema exists, the description fully covers when, how, and what to expect. It provides all necessary context for an agent to use 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 covers the parameter with a basic description. The tool description adds context about the slug format (URL path, not full URL), which is meaningful beyond the schema. Baseline 3 due to high coverage, but extra details warrant a 4.

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 uses a specific verb 'Fetch' and resource 'canonical event' with the identifier 'slug'. It distinguishes from siblings by noting it returns nested markets and is for event grouping, not single markets.

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?

Explicitly states when to use (when you know the slug, need event context) and when not (if only know topic, use search_public or list_events first). Provides clear alternatives and prerequisites.

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