get_catalog_info

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

With no annotations, the description carries the full transparency burden. It clearly indicates a read-only operation (via 'Return') and specifies the outputs, which covers the key behavioral trait. Minor details like potential performance implications are absent, but given the tool's simplicity, the description is reasonably transparent.

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 states the verb and outputs directly. No wasted words; every element contributes to understanding the tool's function.

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 zero-parameter read-only tool with an output schema (which presumably documents the return structure), the description is sufficiently complete. It lists all key outputs (catalog version, product count, snapshot metadata) and requires no further explanation for invocation.

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 zero parameters, and the schema coverage is trivially 100%. The baseline for 0 parameters is 4, and the description appropriately adds no parameter-specific semantics since none are needed.

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 'Return catalog version, product count, and snapshot metadata' uses a specific verb and lists concrete resources, making the tool's purpose unmistakable. It clearly distinguishes itself from siblings like search_products and get_product, which focus on individual product queries.

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 explicit when-to-use or alternative guidance is provided. The intended use (when catalog-level metadata is needed) is implied by the description and tool name, but unlike the TDQS high example, it does not explicitly state exclusions or recommend alternative tools for other scenarios.

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