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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered; the description usefully implies a closed, curated set of followed providers. It says nothing about ordering, pagination behavior, or that the default result set is capped at 100 (that only appears in the schema), which is the kind of operational detail that would earn a higher score.

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 short sentences with zero filler: the resource definition comes first, followed by the actionable tip about the id. Nothing is redundant or buried.

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 simple, zero-required-parameter lookup tool with full schema coverage and a readOnly annotation, the description covers what the resource is and how its output feeds other tools. Only the result-cap/pagination behavior is left implicit in the schema, which is a minor gap.

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% and both parameters are documented in the schema, including the example-driven "Part of the provider name" and the "Omit to list all" behavior. The description adds nothing about `query` or `limit`, so baseline 3 applies.

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 title supplies the verb (List) and the description names the resource precisely, even enumerating what counts as a provider (banks, asset managers, central banks, multilaterals, independent researchers). Siblings all operate on other resources (digests, policy signals, categories, views), so there is no real ambiguity, though the description itself does not explicitly distinguish them.

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?

"Use the id to limit other tools to one provider" gives a concrete downstream use case — fetch provider ids here before filtering other tools — which is exactly the context an agent needs to decide when to call this. It stops short of naming a specific sibling or stating when not to use it.

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