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

Annotations declare openWorldHint=false, but the description directly contradicts this by warning that coverage depends on company name spelling and that the result should be treated as 'strong evidence, not a complete census.' That is explicitly an open-world completeness caveat, so an agent relying on the annotation would draw the wrong conclusion about absent results.

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 compact, front-loaded with the core scope, and every sentence earns its place: scope, unique value, output limits/ordering, and data-quality caveat. No filler or redundancy.

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?

Covers input type, result scope, default/maximum limits, ordering, and a meaningful coverage caveat. While there is no output schema and the exact returned fields are not itemized, the description gives enough context for an agent to invoke the tool correctly, apart from the open-world contradiction.

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 100%, so the schema already documents company, limit, and include_past with defaults and usage guidance. The tool description adds only the conceptual 'name or domain' framing, which is already present in the schema, so it does not materially raise the baseline.

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 precisely what the tool does: given a company name or domain, it returns conferences where that company appears as sponsor, exhibitor, or speaker's employer, covering past and upcoming events. This clearly distinguishes it from sibling tools like events_open_for_sponsorship and get_conference.

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 identifies the exact question this tool answers ('the question no other public source answers') and the correct input form. However, it does not explicitly name alternatives or state when not to use it, so routing relies on the agent's inference from sibling names rather than explicit exclusions.

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