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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is known. The description adds real context beyond that: no emails/phone numbers/manage links are returned, it changes nothing, and non-owned events are 'turned back with a plain message'. It stops short of describing pagination/omission behavior in detail, though guests_limit in the schema covers the truncation note.

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?

Front-loaded with the trigger condition and the return payload, then the negative boundaries and the sibling fallback. Dense but every clause carries information; the parenthetical example questions are slightly heavy but useful for matching agent queries.

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?

Complete for a read-only single-event getter: what it returns, what it deliberately omits, how to obtain the id, the fallback for listing, and the ownership failure mode. No output schema exists, but the description enumerates the return shape well enough for an agent to answer follow-up questions.

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%, so all four parameters are documented in the schema including the default-50/max-500 truncation semantics. The description adds only the pointer on getting event_id via connections_events_list, so the 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 (get) and resource (ONE hosted event by id) and enumerates exactly what comes back: settings, ticket tiers, registration questions, capacity, status, guest list. It is clearly distinguished from connections_events_list and from other event siblings like connections_event_cancel/publish/update.

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 explicit trigger phrasing ('how is my demo day set up', 'how many are coming to X'), names the alternative for listing multiple events (connections_events_list), and states the exclusion case: an event that is not the member's own is rejected. When-to-use, when-not, and how to find the required id are all covered.

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