threads_follower_demographics

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

No annotations are provided, so the description carries the behavioral disclosure burden. The word 'Fetch' clearly implies a read-only operation, and 'for one documented breakdown' hints at the single-parameter constraint. However, it does not describe the return format, pagination, permissions, or any other behavioral details, which is a notable gap with no annotations.

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 a single, front-loaded sentence with no wasted words. The phrase 'one documented breakdown' is slightly ambiguous, but overall the structure is efficient and easy to scan.

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?

This is a simple one-parameter tool with no output schema, so the bar for completeness is moderate. The description plus the enum schema is enough to make an initial call, but it lacks information about return values, how the selected breakdown affects the response, and when this tool is the right choice among sibling analytics tools.

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 description coverage is 0%, and the description does not compensate by explaining the breakdown parameter beyond calling it 'documented.' The schema's enum provides the allowed values (country, city, age, gender), but the description adds little semantic meaning about what each breakdown represents or how the output will be shaped.

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 states a clear verb and resource: 'Fetch follower demographics.' It adds the qualifier 'for one documented breakdown,' which conveys that a single breakdown type is selected, but it does not explicitly distinguish itself from sibling tools like threads_account_insights or threads_post_insights.

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 intended use is implied by the resource name and description: use it when you need follower demographics. However, there is no explicit guidance about when to choose this tool over sibling analytics tools, nor any mention of context such as account-level vs post-level data.

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