list_my_subscriptions

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states the auth requirement and scoping, but omits pagination behavior, response shape, error semantics, and any explicit statement about read-only safety.

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 sentences with no filler; the main purpose is stated first and the auth prerequisite is front-loaded. Every word contributes to describing the tool.

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?

This is a simple list operation, but with no output schema the description should provide more context about what the response contains and how pagination flows. The schema covers the page_token parameter, but the description alone leaves the return structure and retrieval pattern under-specified.

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 100%, with both page_token and max_results fully described in the input schema. The description adds no parameter-specific detail, so the baseline score of 3 applies.

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 clearly identifies the verb ('List'), the resource ('channels the signed-in account is subscribed to'), and the auth context. It allows an agent to distinguish this from siblings like get_subscription_feed based on the channel focus, though it does not explicitly name any alternative.

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 only usage guidance is 'Requires sign-in,' which is a prerequisite but not a directive about when to select this tool versus alternatives such as get_subscription_feed or list_channel_uploads. No exclusions or condition-based routing is provided.

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