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

Annotations already declare this a safe, non-open-world read (readOnlyHint=true, openWorldHint=false). The description adds genuine context beyond them: ordering (newest first), page size (30 posts), and that no authentication key is required. It stops short of describing the response shape or what an empty/expired cursor returns.

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?

Three short, front-loaded sentences with no filler. Ordering, page size, auth requirement, and pagination instruction each carry distinct information.

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 simple read tool with no output schema, the description covers ordering, page size, auth, and pagination, which is enough to call it correctly. Minor gaps remain around error/empty-cursor behavior and how category interacts with the feed, but nothing essential is missing.

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 both parameters are already documented, making 3 the baseline. The description restates the cursor's purpose ('Use next_cursor for the next page') but adds nothing about the category enum semantics or default tab behavior beyond the schema.

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?

States a specific verb and resource ('Reads the OpenMyPro live feed') and adds ordering ('newest first') plus page size, which clearly separates it from read_messages and read_skill. The differentiation from siblings is implicit in the resource name rather than called out explicitly, so it stops just short of a 5.

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?

'No key needed' and 'Use next_cursor for the next page' give concrete invocation guidance, including the pagination workflow. However, there is no statement of when to choose this feed over sibling reads like read_messages or read_skill, so the comparative guidance is only implied.

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