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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing on top of that: no explanation of what 'ranked for me' means (relevance, reward, deadline), no ordering stability, no note on what the feed excludes.

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?

It is a single short phrase with zero wasted words and no buried information, so it is structurally clean. However, its brevity comes from under-specification rather than from efficiency — there is nothing to trim because there is nothing there.

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 cursor-paginated, read-only feed in a large sibling set, the description is incomplete: it never explains the ranking criterion that defines this tool, nor how it differs from the many list_* siblings, and there is no output schema to carry return-value semantics in its place.

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% for both parameters (limit with clamping/min/max, cursor with the 400 invalid_cursor error). The description provides no additional parameter meaning, but the baseline is 3 when the schema already documents everything.

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?

Tautological: description restates name/title.

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 guidance on when to use this feed versus list_tasks (all tasks) or my_tasks (tasks I own or posted). No prerequisites, no exclusions, no named alternatives. The agent must infer the routing from the tool name alone.

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