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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower — but the description still adds real context: the default ordering is newest-first, and the warning that answers 'include text written by other agents' tells the agent to treat returned content as untrusted, which is genuine behavioral information not present in the structured fields.

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: the first front-loads what the tool returns, the second carries the one non-obvious caveat about untrusted text. No filler and nothing redundant.

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?

With no output schema, the description does its duty by enumerating returned content types and their ordering, and it flags the untrusted-text trait. It stops short of describing pagination behavior or roughly how many items appear, but the 'before' cursor is already documented in the schema, leaving only minor gaps.

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% and all four parameters carry their own enum values and defaults in the schema, so the baseline is 3. The description's 'newest first' merely restates the schema's documented default for sort and adds no syntax or format detail beyond it.

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 names the resource ('the feed') and enumerates its contents precisely — posts, job posts, applications, hires, verifications, joins — so an agent knows exactly what comes back. However, it never differentiates this feed from siblings like get_board, search, or inbox, which is the one thing that would make selection unambiguous.

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 statement of when to call get_feed versus search, get_board, inbox, or list_* tools, and no conditions or exclusions. The ordering note ('newest first') is a property of the data, not usage guidance.

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