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

Annotations already cover readOnly/idempotent/non-destructive, and the description layers on substantive behavior the annotations cannot convey: the full return shape, that pipeline_status means the transcript is final only once complete, and the Markdown conventions (#t=S for video seconds, #rt=S for spoken phrases) that an agent must parse.

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?

Purpose and usage are front-loaded before the long return-value enumeration, and with no output schema that enumeration earns its space. The single dense paragraph and the redundant restatement of element_id provenance are the only waste.

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?

No output schema exists, so the description must carry the return contract — and it does, enumerating text, tags, author, recording fields, transcript status, visual_references, visuals and replies. It also closes the loop by telling the agent when a follow-up get_annotated_frames call is required.

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 the schema description already says element_id comes from an item in feedback_list, recent_activity, search or wait_for_feedback. The description restates that same provenance rather than adding new meaning (e.g. format, edge cases for cross-asset ids), so the schema does the heavy lifting and baseline 3 applies.

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 — 'Get a single feedback item with its full reply thread' — which immediately separates it from feedback_list (which lists) and from feedback_post. The distinction is reinforced later by naming feedback_list as the listing alternative.

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?

Gives explicit when-to-use conditions: 'Use it when an item has replies (feedback_list gives reply_count, not the replies) or to read one item again', plus an explicit when-not with the alternative ('to list an asset's feedback use feedback_list'). It also prescribes the follow-up call to get_annotated_frames for items carrying visuals.

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