Get Page Fan Demographics

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint, so the description adds limited behavioral context beyond 'via insights'. It does not disclose important traits like pagination behavior, rate limits, or the fact that the response_format parameter controls output type. No contradiction with 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 brief with two sentences and a list of arguments. No unnecessary information, though the structure could be improved by separating the argument list more clearly or adding a note about the optional response_format parameter.

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 tool has three parameters but the description omits the response_format parameter entirely, which is crucial for controlling output. No output schema exists, so the description should clarify return values or behavior. Given the complexity and low schema coverage, the description is incomplete.

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 33% with only response_format described. The description adds meaning for page_id and metric by explaining their purpose and listing metric values, but it fails to mention response_format or its defaults. It partially compensates for missing schema descriptions but leaves a notable gap.

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 the tool gets fan/follower demographic breakdowns for a Facebook Page, specifying the verb 'gets' and the resource 'fan/follower demographic breakdowns'. It lists specific metric options, distinguishing it from general page insights tools, though it could more explicitly differentiate from siblings like meta_get_page_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?

No guidance on when to use this tool versus alternatives (e.g., meta_get_page_insights or other demographic tools). The description does not mention prerequisites, exclusions, or context for selection, relying solely on implicit understanding of the metric names.

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