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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds modest context by calling it a public feed and defining the stream as the general top-story stream, implying no authentication and no filtering. It does not discuss rate limits, freshness, or article count, so the addition beyond annotations is real but thin.

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?

Three short sentences, zero filler, and the core purpose is front-loaded ahead of the routing guidance. Every sentence earns its place by either defining scope or naming an alternative.

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 parameters, a presence of an output schema, and annotations covering read-only and open-world behavior, the only remaining need is disambiguation from siblings — which the description handles exhaustively. Nothing an agent needs to call this correctly is 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?

The tool takes zero parameters, so by rule the baseline is 4. The description correctly adds nothing parameter-related and does not invent arguments the schema would reject (additionalProperties is false).

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 and resource ('Fetch Breitbart top stories from the public feed') plus the exact scope ('general top-story stream'), which immediately separates it from breitbart_headlines. An agent can distinguish this from its three Breitbart siblings without opening any schema.

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?

Explicit routing rules are given for both alternatives: use breitbart_headlines with a section slug for section-specific lists, use breitbart_sections to discover slugs, and use breitbart_article when a single story's body is needed. When-to-use and when-not-to-use are both covered with no inference required.

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