teams_list_transcripts

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

No annotations are supplied, so the description carries the full burden, and it discloses almost nothing beyond the source types. The truncated fragment hints at newest-first ordering but leaves it unstated; there is no mention of permissions needed, pagination, result limits, or whether transcripts without a transcript-ID are excluded.

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 single sentence is cut off mid-word, so the structure is broken and the most decision-relevant clause (likely ordering or filtering) is lost. Length is short but that is truncation, not concision.

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 no parameters, the description is the only source of truth, and it does not say what a result entry contains or which identifier is needed to call teams_read_transcript. For a zero-arg listing tool that an agent must chain from, this leaves a critical gap.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. The baseline of 4 applies since the empty schema is fully self-explanatory and the description does not need to compensate.

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 gives a specific verb ("Lists") and names two concrete resources: Teams calls started from a chat and calendar meetings that have a transcript. That is far more informative than the bare tool name. However, the text is truncated mid-word ("newes...") and never names the sibling it feeds into (teams_read_transcript), so differentiation is only partial.

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, no prerequisites (e.g. required Teams/M365 connection), and no reference to the obvious follow-up tool teams_read_transcript or to alternatives such as teams_call_history. The agent must infer the discovery-then-read workflow on its own.

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