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

Annotations already declare readOnlyHint, destructiveHint false and openWorldHint false, so safety is covered. The description adds genuinely new behavioral context: the token cost of full transcripts and the fact that the response reveals whether text came from author or machine captions, which determines quotability. That provenance detail is real value beyond the annotations.

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?

Three sentences, front-loaded with what the tool returns, then the efficiency constraint, then the output caveat. Every sentence carries distinct information; the closing 'Read-only' slightly duplicates the annotation but is harmless.

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 output schema, the description takes on the job of describing returns — it does so for provenance and timestamps. It does not explain the unused limit cap of 400, so an agent cannot fully reason about truncation, but otherwise the tool is adequately specified.

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 0%, so the description must carry the parameter burden. It explains the time-range pattern (from/to seconds implied by 'time range' against a 'timed transcript') and that omitting it returns 'the whole thing'. The limit parameter is never mentioned, which is the one meaningful gap.

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 names the resource precisely — 'The material's timed transcript' — so an agent knows it returns timestamped transcript data for a specific material. It does not explicitly distinguish itself from siblings like language_get_material, but the resource is specific enough to identify the tool unambiguously.

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?

It gives concrete operational guidance: 'Ask for a time range rather than the whole thing when you only need one passage — a long transcript is thousands of tokens.' This tells the agent how to invoke it economically. It stops short of saying when to choose this tool over a sibling, so it is clear context rather than true alternative routing.

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