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. The description adds useful context about what is returned (profile fields plus a recent-content feed), but says nothing about pagination, feed size, or what happens with a non-canonical URL. Adequate with annotations carrying the safety profile.

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 sentence, front-loaded with the return payload and closing with the input source. No wasted words or redundancy.

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 one parameter fully documented, an output schema present, and annotations covering safety and open-world behavior, the description only needs to convey scope — which it does. Slightly short of 5 because it omits any hint of feed recency or pagination behavior for the 'recent-content' portion.

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% for the single 'url' parameter, and the description's phrase 'canonical author URL' simply restates the schema's own wording. Baseline 3 is correct since the schema already documents the parameter fully.

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: it returns one Bloomberg author's public profile (name, title, bio) plus their recent-content feed, keyed off a canonical author URL. This clearly distinguishes it from sibling content tools like bloomberg_article, bloomberg_headlines, and bloomberg_news, but it doesn't explicitly name those alternatives.

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: the phrase 'from a canonical author URL' suggests the tool is invoked when you already have an author page URL, presumably harvested from an article. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., use bloomberg_article for a single story).

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