forward_get_catalog

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

With no annotations provided, the description carries the full burden. It states 'list' implying a read-only operation, but lacks details on data freshness, pagination, error handling, or response format. For a zero-parameter tool, the description is adequate but basic.

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 sentence that is concise and front-loaded. Every word is necessary. No redundant or extraneous information.

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, no output schema, and no annotations, the description reasonably covers the tool's purpose. It lists what the user gets (products, criteria, prices). However, it could mention if the list is exhaustive or if there is any filtering, but for a simple catalog listing, it is sufficiently complete.

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?

Tool has zero parameters, and schema coverage is 100% (trivially). The description adds value by specifying what the output includes (products, acceptance criteria, prices), which is more than the schema provides. Baseline for 0 params is 4; the description exceeds by detailing content.

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 uses a specific verb 'List' and clearly identifies the resource: 'Forward's pay-per-result products, acceptance criteria, and prices'. It distinguishes from sibling tools like forward_get_quote (which deals with quotes) and forward_checkout (checkout process).

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 only states what the tool does ('list products...') but provides no guidance on when to use this tool versus alternatives. For example, it does not mention when to use forward_get_catalog instead of forward_get_quote or forward_get_engagement. No explicit context or exclusions.

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