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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and network profile is covered. The description adds that the index is 'public' and updated 'monthly', which is modest extra context. It does not describe pagination, error behavior, or the list's format beyond what annotations imply.

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, front-loaded with the core purpose and then the disambiguation. No filler; every 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?

With an output schema present, the return shape need not be explained, and the annotations carry the safety profile. The description covers identity, scope (historical/monthly), and alternative routing, leaving little an agent still needs. It is only marginally short of complete.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to clarify beyond confirming it is a no-argument listing call.

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 ("List") and a precise resource (Bloomberg's public monthly news-sitemap index), and clarifies it's for discovering historical news feeds. It also names the sibling tools (bloomberg_news, bloomberg_headlines) it is not, so an agent can distinguish it. Not quite a 5 only because 'sitemap index' is jargon that a model must already understand.

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?

Explicitly routes the agent: use this for historical feed discovery, use bloomberg_news or bloomberg_headlines for current stories. This gives both a when-to-use and named alternatives. It stops short of a full 5 because it doesn't state exclusions for the other Bloomberg siblings (article, author, categories).

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