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

No annotations are provided, and the description carries no behavioral details. It does not disclose what happens when the tool is called, whether it is read-only, what data is returned, or any error handling, rate limits, or side effects.

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 extremely short, but this is under-specification rather than effective conciseness. It provides no useful information beyond the tool name fragment and does not earn its place.

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?

With two parameters, no annotations, and no output schema, the description needs to explain the tool's purpose and behavior, but it provides only the word 'Facebook'. This is completely inadequate for an agent to select and invoke the tool correctly.

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 covers 100% of the parameters with descriptions ('Facebook profile URL', 'Set to true to get business hours'), so the baseline is 3. The description itself adds no additional parameter meaning beyond what the schema already provides.

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 is the single word 'Facebook', which merely identifies the platform and restates part of the tool name. It does not state what the tool does (e.g., scrape a Facebook profile) or distinguish it from sibling tools like scrapecreators_facebook_ad_library or scrapecreators_facebook_group_posts.

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?

There is no guidance on when to use this tool or why it should be chosen over any of the over 50 sibling tools. No use cases, prerequisites, or alternative tools are mentioned.

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