meetings_get_transcript

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

Adds meaningful behavioral context beyond annotations: requires the OnlineMeetingTranscript.Read.All permission, resolves multiple input types automatically, and works for attendees even if not the organizer. No contradiction with readOnly/idempotent hints.

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?

Four concise sentences, each serving a distinct purpose: purpose, accepted inputs, attendee support, alternative tool, and permission requirement. Front-loaded with the core function.

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?

Covers inputs, permission, use cases, and the alternative tool. The output format is implied by 'time-stamped speaker turns', though explicit return structure is absent without an output schema. Acceptable for a tool of this complexity.

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 each parameter has a description. The description adds value by explicitly including calendar event id as an accepted format for meeting_id, which the schema does not mention, and clarifies the fallback purpose of event_start/event_end.

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 clearly states it retrieves the spoken transcript of a Teams meeting as time-stamped speaker turns. It distinguishes from siblings by explicitly naming meetings_get_transcript_by_event as an alternative for calendar event ids.

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 usage guidance: use meetings_get_transcript_by_event when only a calendar event id is available, and clarifies this tool accepts join URLs, online meeting IDs, and calendar event ids. Also mentions it works for both organizers and attendees, giving clear context.

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