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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds meaningful behavioral context by defining what the cue map means (segment-to-slide correspondence by index), but says nothing about how alignment is produced, whether it can fail/mismatch, or what the map looks like when empty.

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?

One tight sentence that front-loads the returned entity and then qualifies it with the mapping rule. No filler, though the parenthetical could carry a bit more payload for the space it takes.

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 must convey the return shape; it does sketch the cue map structure, which is the most important thing here. It is still incomplete on parameter meaning (slug) and on edge cases such as missing or unaligned scripts.

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% and the single parameter 'slug' is undocumented in the schema. The description never mentions 'slug' or explains that it identifies the talk/deck, so it does not compensate for the coverage 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?

States a specific verb ('Returns') and a specific resource ('the cue map that links each script segment to its slide'), and even discloses the mapping rule ('segment i drives slide i'). It is clearly not the same as get_script or get_deck, though it does not name a sibling to reinforce the distinction.

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 statement of when to use this tool, when to use get_script/get_deck instead, or any prerequisite (e.g. that a script must already be attached). The agent must infer the use case entirely from the purpose sentence.

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