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

With annotations already covering read-only, idempotent, and safe behavior, the description adds meaningful context: interest-based sorting when preferences exist, fallback to claimed priority plus popularity otherwise, and cursor continuation for the same deck. It does not describe rate limits or the shape of returned items, but those are less critical given the strong annotation coverage.

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 compact and front-loaded: it states the return value, personalization condition, fallback behavior, sibling comparison, and pagination instruction. Every sentence contributes useful information without waste.

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 two-parameter, read-only feed tool with no output schema, the description covers purpose, personalization logic, fallback behavior, default-page context, and pagination adequately. It could do slightly more to clarify what kind of items appear in the feed, but the essential invocation guidance is present.

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%, so the schema already documents both limit and cursor. The description reinforces cursor usage with nextCursor but adds little beyond the schema and does not mention the limit parameter.

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 specific verb and resource: it returns a personalized discovery feed. It explicitly distinguishes itself from the sibling random_feed by saying it is more tailored, and identifies itself as the default discovery page after web login.

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?

It names the alternative random_feed and gives clear context that this is the default discovery page after web login. However, it does not explicitly state when to choose random_feed instead, so it stops short of full when/when-not guidance.

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