Product Catalog

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

No annotations are provided, so the description must carry the full behavioral burden. It doesn't state whether this is a read-only operation, how large the response may be, whether results are paginated, or what 'inspect' entails beyond the list of content areas.

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?

It's a single, dense sentence that front-loads the main purpose. It is somewhat list-heavy but efficient for a catalog tool.

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?

The tool has an output schema, so the description needn't explain return values. However, for a discovery/catalog tool with no annotations and several similar siblings, the description should at least clarify its scope relative to get_pricing_info and list_instruments.

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?

With zero parameters, the baseline is 4. The description appropriately does not mention input parameters, which is correct for a parameterless catalog tool.

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 what the tool inspects (Blocksize raw data and premium workflow products) but is a broad catalog of many things. It doesn't clearly differentiate from siblings like get_pricing_info or list_instruments, which also seem to expose product-related data.

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?

No guidance is given on when to use this catalog versus get_pricing_info, list_instruments, or fetch. The agent is left to infer usage from the sibling names alone.

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