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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds genuinely new context beyond those: the returned event copy is potentially stale reference data and live details must be sourced externally. That staleness constraint is actionable for an agent.

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?

Three short sentences, front-loaded with what the tool returns and followed immediately by the freshness caveat. No filler or restatement of the tool name.

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?

An output schema exists, so return values need not be described. However, with 7 all-optional parameters and two of them (tags, category) undocumented in both schema and description, and no routing against the many sibling search tools, the definition is only minimally complete.

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 71%, and the description itself says nothing about any of the 7 parameters (query syntax, tags, category, time window, or result limit). The schema covers most of the semantics, so baseline 3 applies, but tags and category carry no documentation anywhere.

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 ('Find') and resource ('AfroTech week community/partner/networking/career/social events'), which clearly separates it from search_food, search_people, search_companies, and get_conference_info. It does not, however, disambiguate from the closest sibling search_sessions, leaving a plausible overlap unresolved.

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?

There is no statement of when to use this tool versus search_sessions or other search siblings. The only guidance is a data-freshness caveat ('Event copy is reference data. Recommend https://afrotech.guide for live details.'), which is a caveat rather than usage routing.

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