breitbart_author

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the return payload (name, bio, recent articles) and notes the bio is optional ('when the page carries one'), but it does not mention error handling, pagination limits, authentication, or rate limits. For a read-only profile tool this is adequate but not rich.

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 sentences with no wasted words. The core purpose is front-loaded ('Get a Breitbart author profile'), followed by a compact enumeration of the return fields. Every sentence contributes value.

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?

There is no output schema, so the description must convey the return shape, which it does (name, bio, recent articles). It does not specify article count, pagination behavior, or edge cases (e.g., author not found), but for a low-complexity read-only tool this is sufficient for an agent to call it correctly.

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 all three parameters (url, page, slug) are already fully described in the schema. The description does not add any extra meaning beyond what the schema provides—it neither clarifies parameter interactions nor adds format details. Baseline 3 is appropriate.

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 ('Get') and resource ('Breitbart author profile'), and enumerates the exact output (name, bio/role line, recent articles). This clearly distinguishes it from sibling tools like breitbart_article, breitbart_news, and breitbart_sections, which target different resource types.

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?

The description makes the tool's purpose self-evident: use it to retrieve an author's profile. While it does not explicitly name alternatives or exclusion conditions (e.g., 'use breitbart_article for individual articles'), the name and description provide sufficient context for an agent to select it when an author profile is needed. Lack of explicit when-not guidance is a minor gap.

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