list_live_products

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

With no annotations, the description carries the behavioral disclosure burden. It adds value by specifying the output fields and 'live' status, and 'Free' hints at no cost. However, it does not explicitly state read-only behavior, auth requirements, default limit behavior, or pagination details, which would enhance transparency.

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 two short, purposeful sentences. It front-loads the main action and resource, and every word earns its place with no redundant or vague content.

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 simple list tool with two optional parameters and no output schema, the description provides the resource and output fields, but it omits mention of the kind filter, limit/pagination behavior, and relationship to sibling tools like list_mcp_tools or get_product. This leaves some contextual gaps for an agent deciding to use it.

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 input schema fully describes both parameters (kind and limit), so the baseline is 3. The description does not add any parameter-specific detail beyond the schema; the parenthetical list focuses on output fields, not inputs.

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 states 'List Northern Forge live products' with a specific verb and resource, and enumerates the returned fields (title, url, blurb, monetization). This distinguishes it from siblings like get_product (single item) and list_mcp_tools (a different resource type).

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 phrase 'Free core tool for agents' implies it is a basic, freely available listing operation, but there is no explicit guidance on when to choose this over alternatives such as get_product or popular_tools. No exclusions or when-not-to-use conditions are provided.

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