search_offerings

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 modest context about which offering classes are covered and the historical depth (since 1988), but says nothing about result ordering, what the default 100-row limit implies, or that unpaged result sets can be truncated.

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?

A single front-loaded sentence with no padding or redundancy. It is efficient, though the terseness leaves the usage and behavioral gaps unaddressed rather than the sentence being wasteful.

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 six optional filters, no required parameters, and an output schema handling return values, the description still omits essential calling context: how filters combine, whether partial matching applies to issuer only, and what ordering to expect. For a broad open-world search tool this is under-specified even accounting for the annotation and schema coverage.

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 description coverage is 100%, so every filter (rite, issuer, asset_type, first_date, last_date, limit) is already documented with examples and formats in the schema. The description's only addition is the temporal bound implied by 'since 1988', which slightly informs first_date but adds little 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 clear verb+resource ('Search ... public offerings') plus meaningful scope qualifiers — registered, exempt and restricted categories and a start year of 1988. It does not distinguish itself from adjacent siblings such as issuance_volume or league_table, which also touch the offerings domain, so the agent must infer the boundary.

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 when-to-use or when-not-to-use guidance and no named alternative. The agent is not told whether to reach for this tool versus issuance_volume or league_table when it wants offering-related data, nor what happens when no filters are supplied.

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