Product Catalog

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

With no annotations, the description should disclose behavioral traits like read-only status, authentication needs, or response size. It only lists contents without explaining side effects or data freshness, leaving significant gaps for the agent.

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 a single sentence listing key items, which is reasonably concise. It could be slightly better structured (e.g., separate sentence for upgrade path), but it efficiently conveys the tool's purpose without 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?

Given zero parameters and the presence of an output schema, the description adequately lists what the tool returns. However, it lacks completeness by not specifying that it is a read-only listing or clarifying how the output relates to sibling tools like get_pricing_info.

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 has no parameters, and schema coverage is trivially 100%. The description adds value by explaining what the output includes (products, credits, endpoints, upgrade path), compensating for the lack of parameters and providing context 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 clearly identifies the tool as inspecting the product catalog of Blocksize raw data and premium workflow products, listing specific items like credits and upgrade paths. It distinguishes from siblings like get_pricing_info and list_instruments by focusing on the catalog overview.

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?

The description does not provide guidance on when to use this tool versus siblings, such as get_pricing_info for pricing details or get_market_data_endpoint for endpoint specifics. No explicit when-to-use or when-not-to-use context is given.

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