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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds behavior beyond that: the result is a merge of newest posts with one newest episode per show, ordering is newest first, and supplying a topic silently drops episodes entirely. That last point is a non-obvious behavioral side effect an agent would otherwise miss.

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?

Two tight sentences with the composition rule front-loaded and the filter caveat second. Every clause carries information; there is no filler or restatement of the title.

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 two-parameter, fully documented, annotation-covered read tool, the description covers what is returned at a conceptual level and the one surprising filter behavior. It does not describe the shape of an individual item (fields per post vs. per episode), which would help since there is no output schema, but the omission is minor.

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%, so baseline is 3, but the description earns extra credit by explaining that topic matches a tag and, crucially, that episodes are omitted when a topic is given — a consequence not stated in the schema's 'Only posts carrying this tag.' The limit parameter's interaction with the merged feed is left to the 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?

The description gives a specific verb and resource set: it lists newest posts on brokeit.dev plus the newest episode of each podcast show, newest first. That is far more precise than the title 'Latest news' and makes the combined posts+episodes output clear. It stops short of naming a sibling such as search_news or list_episodes, so the differentiation is implied rather than explicit.

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 is implied by the scope statement (a 'newest items' feed) and by the note that episodes are omitted when a topic is supplied, which is a genuine usage nuance. However, there is no explicit guidance on when to prefer this over search_news, list_episodes, or list_shows, and no stated preconditions.

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