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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description need not re-state it. It adds useful context about data provenance ('Event content originates from third-party ticket providers') and documents the exact return shape, which is genuine value beyond the structured fields.

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?

Two tight sentences with no filler; the core action is front-loaded in the first clause and the return format/provenance follow efficiently. Each sentence earns its place.

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 single-parameter, read-only search tool with an output schema, this is mostly complete. The main gap is the missing differentiation from search_events, which an agent needs to pick the correct tool. Provenance and return format are covered.

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% – the single query parameter is already documented as 'Search query.' With full coverage, the baseline is 3, and the description adds no additional syntax or format detail beyond what the schema provides. Adequate but not additive.

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 ('Search LiveSpot events') and specifies the return format. The title ('Deep Research') and the mention of the OpenAI Deep Research spec provide partial differentiation from the sibling search_events, though the description does not explicitly name that sibling as the alternative.

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?

No when-to-use or when-not-to-use guidance is given. The sibling tool search_events is clearly an overlapping search tool, yet the description never routes the agent between them; the only hint is the 'Deep Research' title, which implies a research-flow context without stating it.

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