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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read, live-page profile is known. The description adds modest value by specifying the returned fields and noting the bio/role line appears only 'when the page carries one', a useful conditional, but it says nothing about pagination behavior despite a 'page' parameter.

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 front-loaded sentence that names the resource and payload with no filler. It is dense but each clause earns its place.

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-value detail is not needed, and annotations cover safety. However, for a three-parameter, zero-required tool the description leaves the input contract entirely unexplained, which is a meaningful gap 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 0% and none of the three parameters (url, page, slug) are mentioned in the description. With zero required params and three undocumented ones, the description does not compensate for the coverage gap or explain how url/slug/page interact.

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 states a specific verb+resource ('one Breitbart author/contributor's public profile') and enumerates the payload (name, bio/role line, recent articles). The 'author' resource distinguishes it from siblings like breitbart_article, breitbart_headlines, and breitbart_sections, though it never names them explicitly.

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 only implied: an agent can infer you call this to fetch an author profile, but there is no explicit when-to-use, no prerequisites, and no routing to alternatives such as breitbart_article for full text or breitbart_sections for section browsing.

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