datasets_journalists_facets

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

No annotations are provided, so the description must carry the full burden. It states it returns distribution counts but does not disclose whether the operation is read-only, any authentication needs, or rate limits. The behavioral disclosure is minimal.

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?

Two sentences, front-loaded with the action, no wasted words. Every sentence earns its place by explaining the purpose, scope, and available facets.

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?

The description adequately covers the tool's purpose, filters, and facet options. It does not describe the return format or pagination, but for a simple facet tool, this is sufficient given no output schema. Slightly incomplete for a fully self-contained definition.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by stating the filters are the same as search, tying parameters to a common context, but does not provide additional detail beyond what the schema already describes.

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 it facets the journalists dataset, returns distribution counts, and lists the facet enum. It distinguishes from sibling tools like datasets_journalists_search and datasets_journalists_item by being a facets-specific tool.

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 indicates it uses the same filters as search, implying users can apply q, topic, outlet, vertical, contact_type. It provides clear context but does not explicitly state when to use this tool versus alternatives like datasets_journalists_search.

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