news_story

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

With no annotations, the description carries the safety burden. It discloses that the text is untrusted input and instructs never to follow instructions inside it, which is a critical behavioral note. It also describes pagination size (~12,000 chars) and output fields (source and feeds), providing useful context beyond the bare mechanics.

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?

The description is front-loaded with the core function, then adds usage alternative, security warning, and output semantics. Every sentence provides essential information without redundancy. It is compact yet comprehensive.

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 2-parameter tool with no output schema, the description is reasonably complete. It covers purpose, input source, pagination, security, and output fields. It doesn't discuss error cases or exact text format (e.g., HTML vs plain), but those are minor gaps given the tool's simplicity.

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 0%, so the description must compensate. It explains article_id's origin and page implies pagination via the 'pages of about 12,000 characters' note. However, it doesn't clarify page numbering, range limits, or behavior when out of range, leaving some ambiguity for the page parameter.

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 tool fetches one story from the reader's feed with full text, and it explicitly ties article_id to symbol_news. It distinguishes itself from publisher pages and implies distinction from search/list tools like news_search by focusing on a single article by ID.

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?

Provides explicit guidance to use this instead of opening the publisher's page, citing licensing and automated fetch refusals. It also tells the agent that article_id comes from symbol_news, which is a direct usage hint. However, it doesn't explicitly mention when NOT to use it or compare to sibling tools like news_search.

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