list_livetv_sessions

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the endpoint path and filter parameters, but does not disclose any additional behavioral traits such as pagination, limits, ordering, or response size. It adds minimal context beyond 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?

The description is short and front-loaded with the main action 'Get all sessions'. The extra lines describing the endpoint and parameters are efficient and scannable. No wasted words.

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?

Given it's a simple read-only list operation with two optional filters and an output schema exists, the description is nearly complete for basic calling. It lacks guidance on response structure (though output schema exists), and does not cover edge cases like how filters interact (AND vs OR) or whether results are sorted. Overall, adequate but with minor gaps.

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%, but the description lists both parameters with their purpose: 'Filter by DVR ID' and 'Filter by channel ID'. This matches the schema properties. The description adds meaning beyond the raw schema by stating they are filters, so it compensates somewhat, but does not elaborate on value format or constraints.

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 says 'Get all sessions' and provides the endpoint path, which clearly indicates it retrieves LiveTV sessions. It distinguishes from sibling tools like 'get_livetv_sessions_by_session_id' (specific session retrieval) and 'list_livetv_recordings' by focusing on sessions. However, it doesn't explicitly define what constitutes a 'session' or the scope, but it's clear enough.

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?

The description mentions optional filters (dvr_id, channel) but does not state when to use this tool versus alternatives like 'list_livetv_recordings' or 'get_status_sessions'. No guidance on when not to use it or when to prefer a sibling.

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