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

No annotations exist, so the description bears the full burden. It usefully discloses the return shape and adds a semantic caveat ('Specialties describe supported categories, not open bids') that prevents misreading the data, but says nothing about ordering, size, caching, or rate limits for what could be a large catalog.

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?

Three short sentences, front-loaded with what the tool returns, then the follow-up usage hint, then the one-line caveat. Every sentence carries distinct information with no repetition of the name or title.

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 return contract, and it does enumerate the fields and the daily count. It is nearly complete; only secondary details like ordering or catalog size are absent.

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 is nothing for the description to disambiguate; the baseline of 4 applies. The description concerns itself entirely with output content rather than parameters, which is appropriate here.

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 the resource (the trade catalog) and enumerates the per-entry fields (id, name, description, specialties, search aliases) plus today's open count, so an agent knows exactly what this returns. It distinguishes itself from the sibling search_opportunities by positioning itself as the id/alias source that feeds it, though the verb is implied by 'catalog' rather than stated.

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 a concrete downstream instruction ('Use an id or any alias in search_opportunities'), which implies this is a lookup-first tool, but it never states when to call this versus list_documents, list_set_asides, or corpus_stats, nor any exclusion. Usage is inferable rather than explicit.

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