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 useful context that it returns public metadata plus body paragraphs, but it omits notable operational caveats for Bloomberg specifically, such as paywalled/truncated body content or access requirements.

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?

Three short sentences with the purpose front-loaded and the alternatives following; every sentence earns its place and nothing is padded.

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?

For a single-parameter read tool with an output schema and readOnly/openWorld annotations, the definition covers what is needed to select and invoke it. The only real gap is guidance on where to obtain the canonical URL and whether body content is subject to paywall limits.

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?

With a single parameter at 100% schema coverage, the schema already documents 'url' as a canonical Bloomberg article URL, and the description only echoes this. Baseline 3 is correct since the description adds no syntax, format, or validation detail beyond the schema.

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 gives a specific verb (Fetch) and resource (one Bloomberg article's public metadata and body paragraphs) and specifies the input shape (canonical article URL). It is immediately distinguishable from bloomberg_headlines and bloomberg_news, which it names.

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?

It explicitly routes the agent to two alternatives: bloomberg_headlines for discovering story cards and bloomberg_news for the general feed, implying this tool is used once a canonical URL is in hand. It lacks an explicit when-not condition or a statement of where the URL should come from, but the alternative routing is clear.

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