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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds two genuinely new facts: the operation requires the `content:read` scope, and returned user-written text lands in `untrusted_fields` and must be treated as display-only data rather than instructions — a meaningful behavioral disclosure 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 short sentences, zero filler, with the core action stated first and the security caveat second. Nothing could be removed without losing 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?

For a single-parameter read tool with full annotation coverage, the definition supplies the auth scope and the untrusted-content handling rule, which are the main things an agent needs. The remaining gap is identifier semantics and any hint about the returned event's shape, which is minor without an output schema.

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?

The schema has one required `id` parameter with 0% description coverage, and the description never explains what kind of identifier it is (live event id vs. some other reference) or its expected format. With schema coverage at zero, the description needed to compensate here and does not.

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 names a specific verb and resource ("Get a live event"), so an agent knows it is a single-item fetch rather than a listing. However, it adds nothing beyond the title and does not distinguish itself from nearby siblings such as list_live_events or preview_live_event.

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 guidance on when to use this versus list_live_events, preview_live_event, or get_booking_event. The only contextual signal is the permission requirement, which is an access precondition rather than a when-to-use rule.

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