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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), and the description adds real value on top: it discloses that the bundle consolidates multiple reads into one call and explains what the rows flag changes. The one weak spot is that "Pass rows true for each part's full rows" understates the truncation the schema describes (parts are cut to fit with a pointer to read on), so the agent could misjudge whether it is getting complete data.

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 what-is-returned clause is front-loaded and the usage condition follows immediately, so the agent gets selection logic in the first two sentences. The remaining two sentences on rows and alternatives are necessary, though the second sentence is slightly dense with comma-swamped enumeration and the rows sentence is terse enough to be ambiguous.

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 read-only aggregator with no output schema, the description says enough about shape (summary vs. rows), scope (one event), and the bundled parts. The currency and range mechanics live entirely in the schema, which is fine, but the description never mentions that the response may be truncated per part, which is the one behavioral fact an agent genuinely needs up front.

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%, with rows, parts, range and currency all documented in detail, so the schema carries most of the semantic load. The description adds only a thin layer, restating the rows toggle and implying that omitting parts yields all three, which the schema already says explicitly. Baseline 3 is appropriate here.

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?

The description opens with a specific verb and resource ("Returns a short summary of one event in one call") and then enumerates exactly which parts are bundled: headline prices, listings, demand, series start/end/low/high, and top sections. This states precisely how it differs from the three single-part siblings, so an agent can select it without opening any schema.

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?

"Use it when the person wants an overview of one event that needs more than one of those parts" gives a concrete selection condition, and the closing sentence names all three alternatives (get_event_analytics, get_event_chart, get_event_sections) with the distinguishing property that each reads one part in full. When-to-use, when-not-to-use, and alternatives are all present.

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