trmnl_get_playlist_item_schedule

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered structurally. The description's extra contribution is just the raw endpoint, and it says nothing about what the schedule representation looks like or what an item with no explicit schedule returns.

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 short lines, with the functional statement front-loaded ahead of the endpoint reference. No wasted prose, though the 'TRMNL GET /api/...' fragment is somewhat opaque formatting.

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 carries responsibility for describing the return value, yet it never says whether the response is a list of time windows, a boolean, or an empty result when unrestricted. For a read tool with a nested required path object, that is a meaningful gap.

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 only 50%, and the description supplies no parameter meaning at all — it never explains that item_id identifies the playlist item whose schedule is fetched, or what the profile parameter selects. It relies entirely on the partially documented nested schema.

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 concrete verb and resource: read the schedule governing when a specific playlist item may display, plus the backing endpoint GET /api/playlists/items/{item_id}/schedule. That is clear enough to distinguish it from the write-side sibling trmnl_replace_playlist_item_schedule, though the sibling is never named.

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 explicit guidance on when to use this versus trmnl_replace_playlist_item_schedule, trmnl_list_playlist_items, or trmnl_get_playlist_item_preview. The 'Read' wording implies inspection-only, but the agent must infer that from the tool name rather than the description.

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