team_transcript

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

With no annotations, the description carries the full behavioral burden and does not state that this is read-only, whether it paginates, how 'limit' truncates output, or what happens when session_id is unknown. It discloses only the output serialization choice, leaving the operational profile largely undocumented.

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?

A single well-formed sentence with the resource and the output-format choice front-loaded; nothing is wasted. It is arguably too terse given the four undocumented parameters, but the sentence itself is efficient.

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?

An output schema exists, so return values needn't be explained, but for a 4-parameter tool with zero schema coverage and no annotations the description should at minimum explain limit/pagination and session identity. As written, an agent cannot predict transcript size or scoping behavior.

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%, so the description must compensate and it only clarifies 'fmt' (JSON messages vs rendered Markdown). The meaning of workspace_path, session_id, and especially limit (200 default — per-page? max messages? truncation point?) is left entirely unexplained.

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 ('Read a team session transcript') plus the two output forms (JSON messages or rendered Markdown), which separates it from siblings like team_report and team_decisions that aggregate rather than dump raw sessions. It doesn't explicitly name which sibling to prefer for summary-style needs, so it stops short of a 5.

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 guidance on when to call this versus team_report, team_decisions, team_compare, or team_status, all of which operate on team session data. The agent must infer from the name alone that this is the raw-transcript option.

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