teams_read_transcript

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about permissions required, whether the transcript is returned in full or truncated, or how large/long transcripts are handled. The one useful disclosure is the scope of supported sources (chat-originated calls and calendar meetings), which is genuinely additive but far short of what a no-annotation tool needs.

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?

It is a single short sentence with the resource front-loaded, which is the right shape. However, it terminates mid-parenthetical, so the one sentence it does have is not actually complete.

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 annotations, no output schema, and an empty input schema, the description is the only source of truth and it is both truncated and silent on return shape, size limits, and how to obtain the transcript_id it refers to. An agent cannot reliably invoke this tool from the definition as given.

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?

The schema declares zero properties, yet the description references a 'transcript_id' argument, so the text and the structured input disagree about what the caller must supply. Beyond naming that identifier, no format, source, or example is given, leaving the agent unable to construct a valid call from the schema alone.

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 ('Reads the transcript') and narrows the scope to Teams calls started from a chat or calendar meetings, which separates it from broader siblings like teams_list_transcripts or teams_read_chat_messages. The sentence is cut off mid-clause, so the scope statement is left hanging rather than fully resolved.

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?

There is no explicit when-to-use guidance and no mention of the sibling that produces the identifier this tool needs (teams_list_transcripts). The reader must infer that a transcript must first be located elsewhere before calling this, and nothing distinguishes it from zoom_read_transcript or teams_list_transcripts.

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