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 structurally. The description adds value by characterizing the payload as a 'public' profile with name, optional image, and recent story cards, but says nothing about auth needs, rate limits, or failure modes when a slug is invalid.

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 action and resource front-loaded and the input requirement immediately following. No filler, no restatement of the tool name.

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?

Output schema exists, so the return-value sentence is bonus rather than necessity, and annotations cover the read-only profile. The gap is the input contract: with two unlabeled, non-required parameters, the description should clarify the slug-vs-url relationship, and it does not.

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% with two undocumented parameters. The description explains where a slug comes from but never mentions the 'url' parameter at all, and since zero parameters are marked required, it leaves the agent guessing whether slug and url are alternatives or jointly required.

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 a precisely scoped resource (one The National author's public topic profile), and even enumerates the returned content. That resource is clearly distinct from its siblings national_article, national_headlines, and national_news, so an agent can route without opening schemas.

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?

Gives a real workflow hint for obtaining the required identifier ('a slug from an article byline or canonical profile URL'), which tells the agent both the context of use and where the input comes from. It stops short of naming alternatives or stating when not to use this tool, so it does not reach the 5 bar.

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