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

Annotations already cover read-only and open-world behavior, so the bar is lower. The description adds genuinely useful context that the recent-article list has no pagination, which the annotations do not convey. It doesn't describe rate limits or return shape, but that's minor given the output schema.

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 tightly written sentences with zero filler. The core action and inputs come first, followed by the pagination caveat and the sibling routing, all front-loaded and earned.

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 an output schema present, return values need no explanation, and readOnly/openWorld annotations cover the safety profile. The description adds the no-pagination caveat and the sibling alternative, making it nearly complete; only a note on slug-vs-url precedence 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?

Schema description coverage is 100%, so both slug and url are already documented in the schema. The description restates that slug or url may be used but adds no format or precedence detail beyond what the schema provides, so baseline 3 applies.

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 (a Politico staff author's public profile and recent bylined article items), and explicitly names the sibling politico_article to contrast with. An agent can distinguish it from the other politico_* tools without opening the 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?

Explicitly routes the agent to politico_article when a single story's details are wanted, and clarifies the two accepted inputs (slug or canonical url). It lacks a broader when-not statement relative to siblings like politico_headlines, so it stops short of a 5.

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