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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-fetch behavior are covered by structured data. The description adds that the payload includes metadata and body paragraphs, which is modest value beyond the annotations. It omits any note about URL validity requirements or coverage limits of 'public' articles.

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, well-formed sentence that is front-loaded and free of filler. It is appropriately sized for a one-parameter read tool, though the terseness is partly responsible for the missing parameter guidance.

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, the description needn't explain return fields, and annotations cover the safety profile. However, the sole required parameter's expected format is undocumented, which is a real gap for correct invocation of an otherwise simple tool.

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 0% for the single url parameter, so the description carries the full burden and fails to compensate. It doesn't state that url must be a ProPublica article URL or give any format example, leaving the agent to guess the expected value.

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 names a specific resource and scope: a single ProPublica article's metadata and body paragraphs. This distinguishes it from siblings like propublica_headlines, propublica_news, and propublica_sections, which serve broader/lists. It's clear without an explicit verb, but the noun phrase conveys the fetch-one-article action well.

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?

There is no when-to-use guidance, no stated prerequisites, and no mention of when a sibling (e.g., propublica_headlines for browsing, propublica_author for attribution) would be preferable. The agent must infer usage entirely.

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