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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read and live-feed nature are covered structurally. The description adds only modest context (that it returns headline items from the general stream) and says nothing about pagination, freshness, or result volume for the public feed.

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 tight sentences, front-loaded with what it does and followed by the routing guidance. Every sentence earns its place and none repeats structured data.

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 no-parameter feed tool with an output schema, the description gives all an agent needs: purpose, scope, and which sibling to use for the adjacent tasks. Return-value detail is correctly left to the output schema.

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?

The tool takes no parameters, so there is nothing for the description to clarify. The description correctly indicates the tool is unfiltered (general stream) while pointing to parameterized siblings, which is appropriate given the zero-parameter 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 (fetch) and resource (ProPublica top stories from the public feed), and explicitly delimits the scope as the 'general top-story stream' rather than a section-specific list. This distinguishes it from propublica_headlines.

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?

Explicitly routes the agent: use propublica_headlines for section-specific lists, propublica_sections to discover slugs, and propublica_article when a single story body is needed. When-to-use and alternatives are all named.

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