Get Feed Briefing

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the tool returns one headline per tag, caps at 8, and includes a 'render field with tiered rendering guidance'. This goes beyond basic purpose to explain output behavior. It doesn't mention read-only nature but is implied.

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?

Four sentences, each adding unique value: core function, constraints, usage context, and response trait. No wasted words, front-loaded with purpose. Efficient and well-structured.

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?

Given the tool has one optional parameter and no output schema, the description explains the output (headlines, capped, one per tag, render field). It could benefit from listing exact response fields, but the mention of 'render field' provides enough guidance for an AI agent to compose a reply. Sibling context is handled.

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 coverage is 100% with one optional parameter 'max_headlines'. The description adds meaning by stating 'capped at 8 total' and confirming the default, reinforcing the parameter's role in limiting output. It adds value beyond the schema's description.

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 clearly states the verb ('Generate'), resource ('compact headline briefing from pinned feeds'), and constraints ('one headline per tag, capped at 8 total'). It distinguishes from siblings like 'get_feed_items' and 'get_session_start' by noting it is designed for the morning dashboard and only fetches pinned feeds.

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?

The description explicitly says 'Designed to be included in get_session_start without slowing it down' and 'Only fetches pinned feeds', providing clear usage context. It implies when not to use (e.g., for non-pinned feeds or detailed feed reading), though it does not explicitly list alternative tools.

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