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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add behavior beyond that. It does: result ordering ('largest company lists first'), the fields returned, and the implicit default that omitting year/month limits results to upcoming events. Return-format detail is partly redundant with the output schema but the sort order and default scope are genuine additions.

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 sentences, front-loaded with purpose, then return contents, then the default-scope rule. Dense with value and no filler, though the enumerated return fields are the longest block and slightly overlap the output schema.

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?

For a zero-required-parameter search tool with a full output schema, the description covers scope, filter semantics, default behavior, ordering, and return contents. An agent has everything needed to call it correctly without inspecting siblings.

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 coverage is 100%, so the baseline is 3; the description earns a bump by giving value examples for topic and location ('fintech, healthcare, AI', 'Las Vegas, Germany or Europe') and by explaining the behavioral consequence of omitting year and month, which is parameter-level semantics not present in 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 (find/search) and resource (conferences and trade shows) plus the filter axes (topic, place, year, month). Concrete examples like 'fintech conferences in 2027' or 'events in Las Vegas in March' make the scope unambiguous and clearly differentiate it from the get_* siblings that fetch single known entities.

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?

Gives clear usage context through worked examples and explains the default scoping rule ('With no year or month it returns upcoming events only'). It never names the alternative sibling tools (get_conference, get_company_conferences, get_conference_sponsors) or states when not to use search, so it falls short of explicit when/when-not guidance.

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