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

Annotations already declare this is read-only, non-destructive, idempotent and closed-world, so the safety profile is covered. The description adds that the datasets are 'bounded' with explicit filters and limits, which is useful context, but it does not explain what the bounds are or what calling this actually returns.

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, front-loaded sentences with no filler: the resource is stated first and the 'Offline' qualifier is appended. It is terse to the point of being telegraphic, but nothing is wasted.

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 no parameters and no output schema, the description must carry the whole burden of explaining what the agent gets back, and 'their coverage, filters and limits' only partially does so. It never clarifies how the returned catalog relates to the query/route/review siblings, which is exactly what an agent would need to chain tools correctly.

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 there are no argument semantics to document; the rubric baseline for a 0-param tool is 4. Schema coverage is 100% and nothing in the description conflicts with the empty 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 ('Discover') and resource ('seven bounded OpenBB datasets') plus what the discovery covers ('coverage, filters and limits'), so the tool's job is unambiguous. It does not, however, differentiate itself from the closely-named sibling financial_evidence_sources, leaving ambiguity about which catalog to call.

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?

There is no guidance on when to reach for this tool versus financial_evidence_sources, financial_evidence_query, or the other catalog/query siblings. The word 'Offline' hints at a static local lookup but is not framed as a usage condition or alternative.

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