discover_events

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions DEMO MODE and a registration link for unlimited runs, but does not describe the output format, whether the tool modifies data, rate limits, or other side effects. The description is insufficient for an agent to understand behavior beyond basic discovery.

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 two sentences, front-loading the purpose and following with demo mode info. It is appropriately sized with no wasted words, though the second sentence is somewhat promotional.

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 3 parameters, no output schema, and no annotations, the description should explain what the tool returns and how it behaves in demo vs full mode. It fails to describe the return format (e.g., a list of events with key details) and only hints at limitations through the registration link. The description is not complete enough for an agent to fully understand capabilities.

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 67% (2 of 3 parameters have descriptions). The description adds context by listing event types (conferences, webinars, meetups, podcasts) which aligns with the 'kind' enum, but does not provide additional meaning for the 'limit' or 'niche' parameters beyond what the schema already states.

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 tool discovers live conferences, webinars, meetups, and podcasts in a niche, with a specific verb (discover) and resource (events). It distinguishes from sibling discover_communities by focusing on events rather than general communities.

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 mentions DEMO MODE works without an API key, providing a condition for use, but does not explicitly state when to use this tool vs alternatives like discover_communities or draft_outreach_for_event. Guidance is minimal beyond the demo limitation.

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