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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and freshness characteristics are covered. The description adds the 'public section' scoping constraint, but nothing about ordering, recency window, or pagination behavior beyond that.

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?

A single sentence with zero waste, front-loading what the tool returns before the prerequisite constraint. Nothing extraneous.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The prerequisite chain and scope are stated, leaving only minor gaps (recency, ordering) that are not critical for correct invocation.

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 description coverage is 100% and the slug values are enumerated in the schema, so the baseline is 3. The description adds one piece of meaning beyond the schema – that the value must originate from breitbart_sections – which is a useful constraint but not a syntax or format detail.

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?

Specific verb-resource pairing: 'Current Breitbart headlines' for 'one public section'. The scope qualifier 'one public section' narrows it usefully. It names breitbart_sections as the source but does not distinguish itself from breitbart_news, the closest sibling.

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?

States the prerequisite clearly – section 'must come from breitbart_sections' – which routes the agent to the correct sibling first. It stops short of saying when to prefer headlines over breitbart_news or breitbart_article, so no explicit exclusion.

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