df_catalog

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

With no annotations, the description carries the burden; it does disclose that the call is free and that it returns price-per-call plus return descriptions, which is meaningful behavioral context. It stays silent on catalog size, pagination or freshness, leaving gaps for a listing tool.

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 with zero waste; the free/cost signal is front-loaded followed immediately by the resource and payload.

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 listing tool with no output schema, the description explains what each entry contains (price per call, return values), which is enough for correct invocation. A brief note on catalog scope or freshness would complete 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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies.

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?

Specific verb (List) plus resource (DF Market Intelligence data tools), and it further specifies the payload — price per call and return values. This clearly distinguishes it from siblings like df_status and df_wallet, which serve different roles.

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 leading 'Free.' hints that this is a zero-cost discovery call, implicitly useful before invoking paid tools, but no explicit when-to-use or when-not-to-use guidance is given. The agent must infer that this is a catalog/bootstrap step.

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