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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description goes well beyond them by disclosing the entry taxonomy (item, job_of_the_day, blog, broadcast) and the semantics of flags such as isStarred:false meaning the user unstarred the company. With no output schema, this return-shape disclosure is exactly the behavioral context an agent needs.

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 front-loaded with the core statement of what the feed is, and the dense parenthetical enumerations each carry distinct information rather than padding. It reads as a long run-on with heavy nesting, which slightly hurts scannability but wastes little text.

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 carries the burden of explaining return values and does so thoroughly, covering each entry kind, per-role fields, and the meaning of flags, while fully accounting for both parameters including pagination limits. Nothing an agent needs to call this correctly appears to be 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 and the baseline is 3. The description adds round-trip meaning to the cursor parameter ('pass nextCursor back to page deeper; omit it for the newest page'), which clarifies the intended paging workflow beyond the schema's field-level text.

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 a specific resource (the user's dashboard feed) and describes it as a single composed stream that is chronological newest-first, so the agent knows exactly what is returned. It does not name or distinguish itself from siblings like get_digests, get_saved_jobs, or search_jobs, which would be needed for 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?

Usage guidance is limited to pagination mechanics (pass nextCursor to page deeper, omit for the newest page) and a soft content hint that blog/broadcast are 'usually skim'. There is no explicit when-to-use-this-vs-alternatives framing against the sibling list tools (get_digests, get_starred_jobs, search_jobs), so usage is only implied.

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