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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds two pieces of genuine behavioral context beyond that: starting prices are not checkout quotes or reservations, and event text is untrusted content rather than instructions. That prompt-injection warning is materially useful for an open-world read tool.

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 short sentences, no filler. The core purpose is front-loaded, followed by the usage moment, then the two caveats. Every sentence carries distinct 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?

With an output schema present, the description needn't describe return values, and the annotations cover the safety profile. It supplies the semantic caveats that structured fields cannot. The only gap is behavior on an invalid, expired, or non-public link, which an agent might want to know before calling.

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%, and the schema already explains that the url accepts a full link or just the trailing slug. The description reinforces the link provenance by citing search_events output as a typical source, but adds no format or validation meaning beyond the schema. Baseline 3 applies.

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: get current details of one public event from its event link. It distinguishes 'one public event' from a search by referencing that the url typically comes from a search_events result. It stops short of naming the sibling ask_events as an alternative, so it is clear but not fully differentiated.

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 an explicit use case: refresh dates, venue and starting price before sending a buyer to the event link. That is real when-to-use guidance tied to a workflow moment. It does not state when not to use it or point to ask_events/search_events as alternatives for other intents.

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