stellaris_video_chapters

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

No annotations are provided, so the description carries the full burden. It usefully discloses the shape of the result (chapters with timestamps and deep links) and the read-only nature is implied by 'List', but it says nothing about ordering, pagination, permissions, or behavior when the video substring matches multiple or zero videos.

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?

Two sentences, front-loaded with the core action and result, then the use case. Nothing is redundant or padded.

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?

For a simple one-parameter read tool with no output schema, the description is nearly sufficient. The one gap is that the schema's 'omit to list all ingested videos' is ambiguous for a chapters tool (all chapters of all videos?) and the description doesn't resolve it.

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 single optional 'video' parameter is fully documented in the schema, including the omit-to-list-all behavior. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 ('List the chapters of an ingested video') and names the payload ('timestamps and deep links'), which distinguishes it from stellaris_video_search and stellaris_outline. It does not name those siblings explicitly, so the differentiation is inferable rather than stated.

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?

'Use to point a player at the right section of a long tutorial' gives a concrete scenario, but there are no exclusions or named alternatives (e.g., when to use stellaris_outline instead). Usage is implied by context rather than specified.

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