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. The description adds genuine behavioral context beyond that: the date format (YYYY-MM-DD) and the caveat that relative dates may be omitted, which helps the agent interpret results. It stops short of describing pagination or freshness of the article list.

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 zero filler; the core action is front-loaded and the data-format caveat follows. Every sentence 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?

With an output schema present, return values need not be explained, and read-only/open-world annotations cover the safety profile. The description is nearly complete for a single-parameter read tool; only minor gaps (list size or pagination) remain.

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 coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by indicating a slug is also acceptable, whereas the schema documents the field only as a 'Canonical BBC News correspondent URL' — useful disambiguation of accepted input.

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), resource (BBC News correspondent profile), and enumerates what is returned (name, short bio, recent articles). The resource is clearly distinct from siblings like bbc_article, bbc_headlines, and bbc_search, so an agent can select it 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?

The description implies usage by noting the profile is fetched 'by author URL or slug,' which tells the agent the accepted input form, but it offers no explicit when-to-use or when-not-to-use guidance versus bbc_search or bbc_article. Usage is implied rather than stated.

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