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

Goes well beyond the readOnly/non-destructive/closed-world annotations by disclosing the 403 behavior with the details.opensAt field, the 404 case when no details exist, a stricter-than-normal rate limit ('the detail limit'), and cache/robots headers. This is exactly the error- and access-behavior context annotations don't carry.

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-loads the purpose and then stacks constraints, each sentence carrying distinct information. It is dense and slightly run-on (timing, 403, 404, rate limit, headers in one paragraph), but nothing is filler.

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 no output schema, the description supplies the return contents, the failure modes, the temporal window, and the caching semantics — everything an agent needs to call this correctly and interpret non-200 responses. The only gap is the unresolved 'slug' parameter, which is a schema-side omission.

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 0% and the single required 'slug' parameter is never mentioned in the description — no format, no source, no distinction from other event identifiers. With low coverage the description is expected to compensate, and it 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?

States a specific verb ('Get') and resource ('an online event's join details') and immediately enumerates what those details are (link, meeting ID, passcode, phone), which distinguishes it from get_event and get_event_contact. An agent can tell exactly what this returns without opening the 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?

Gives an explicit availability window — only from 30 minutes before the next occurrence's start until it ends — and what happens outside it (403). It does not name any sibling as an alternative for related data (e.g. get_event or get_event_contact), so routing guidance is strong but not complete.

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