list_media_subscriptions_scheduled

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

Annotations already cover read-only, idempotent, open-world, non-destructive behavior. The description adds only the GET endpoint and the 'all' scope; it does not disclose pagination, authentication, or what counts as 'scheduled,' so it offers little behavioral context 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?

The description is two compact lines: a front-loaded action sentence and the REST path. Every part earns its place, with no redundant explanation.

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 zero-parameter read-only listing with a rich annotation set and an output schema, the description is largely sufficient to select and invoke the tool. It is slightly thin on explaining how 'scheduled recordings' relates to the subscription model, but that is a minor 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?

There are zero parameters, so the empty schema is already complete and the description has no parameter meanings to clarify. The baseline of 4 applies because there is nothing to compensate for.

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 states a clear action and resource: 'Get all scheduled recordings.' The word 'scheduled' distinguishes this from the many media-subscription list tools, though it does not explicitly name siblings such as list_media_subscriptions.

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 provides no guidance on when to use this tool versus list_media_subscriptions, list_media_subscriptions_template, or get_media_subscriptions_by_subscription_id. It only defines what the endpoint does, leaving the agent to infer selection criteria from the tool name.

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