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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds meaningful non-obvious behavior: catalog metadata is not observations and is not a permission grant, universes contain membership only, and certain data classes are out of scope. Those are exactly the constraints an agent needs before treating results as data access.

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?

The description is dense but front-loaded: discovery mode first, then describe mode, then scope boundaries. Every sentence carries a distinct constraint or usage rule, and there is no filler.

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 read-only discovery/describe tool with no output schema and partially documented parameters, the description supplies the missing conceptual context: what discovery returns conceptually, what datasetId inspection yields, what the catalog is not, and where it should not be used.

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 67%, so several parameters are already documented. The description adds value by explaining the datasetId-only mode and what it returns (contract, schemas, units, coverage, historical guarantees), but it does not explain limit, cursor, source, or operations behavior beyond what the schema already says.

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 and resource ('Find BotSpot-provided public research datasets') and distinguishes the two operating modes: list matches vs. describe a single dataset by datasetId. It also draws a clear line between catalog metadata and actual observations, which separates it from data-query siblings.

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 gives explicit when-to-use guidance ('versioned symbol-membership universes, public news discovery, or when unsure whether SEC, Treasury, BLS, BEA, OFR, or CFTC is the right source') and explicit exclusions ('does not provide real-time prices, broker data, or premium news'). That is close to a full routing rule for the agent.

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