meetings_get_transcript_by_event

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by explaining the resolution process, the time-based fallback for attended meetings, and the required permission scope (OnlineMeetingTranscript.Read.All). These behavioral details go beyond the structured annotations.

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 description is front-loaded with the main purpose, followed by usage context, optional input behavior, fallback logic, and a permission note. All five sentences are purposeful, though slightly verbose. Still concise and well-structured.

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?

Given that there is no output schema, the description sufficiently covers the tool's behavior and use cases. It explains the resolution chain, fallback, permissions, and optional shortcuts. It could mention the return type, but the description is otherwise complete for a read-only transcript retrieval tool.

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 each parameter described. The description text adds meaningful context: event_id is the primary starting point, join_url skips the event lookup, and online_meeting_id skips both lookup and filter steps. This explains the relationship between parameters, exceeding the baseline for high schema coverage.

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 specifies a clear action: 'Get a meeting transcript starting from a calendar event id', and details the resolution path (event → join URL → online meeting). It distinguishes itself from siblings like meetings_get_transcript and meetings_get_from_join_url by its explicit starting point and lookup steps.

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?

Provides explicit guidance: 'Use when an event id from the calendar tools is all that is available.' It also explains optional inputs to skip lookup steps and the fallback time-based matching behavior. Does not name alternative sibling tools explicitly, but the usage context is clear.

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