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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description usefully adds that event copy is reference data and may not reflect live details, which is non-obvious context, but says nothing about result ordering, pagination, or how many results a broad query returns.

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, no filler, with the scope-defining clause front-loaded and the data-freshness caveat placed immediately after. Every sentence carries information.

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 fields need not be described, and the description covers scope plus the reference-data caveat. For a 7-parameter search tool it is largely sufficient, though the relationship to search_sessions and the meaning of tags/category remain unaddressed.

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%; the date/time and limit parameters are well documented in the schema itself (including an anti-probing instruction on limit), but tags and category have no descriptions in either place. The description's category list (community/partner/networking/career/social) hints at valid tag/category values, which adds marginal meaning over the schema.

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 and resource ('Find ... events') and narrows the scope to AfroTech week event categories (community/partner/networking/career/social), which separates it from search_food, search_guide, and search_people. It stops short of explicitly distinguishing itself from the nearby sibling search_sessions, so an agent must infer the events-vs-sessions split.

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, search_guide, or plan_conference_week. The only usable guidance is the pointer to afrotech.guide for live details, which is a data-source caveat rather than a routing rule.

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