Server Quality Checklist

Tool Scores

• hasdata_facebook_profile_getFacebookProfileA
  4.1/5.0
  Behavior4/5

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

  With no annotations, the description carries the behavioral burden. It discloses that only public pages/profiles are supported, that feed pagination walks 'three posts per request via pagination.nextPageToken,' and that the counts are exact ('exact likes and talking-about counts'). This is substantive behavioral context beyond the schema, though it omits rate limits or failure behavior.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is front-loaded with the operation and return fields, then gives pagination behavior and usage scenarios. The opening 'Get Facebook Profile' is redundant with the title, and the return-field sentence is long, but the content is dense and useful rather than padded.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Since there is no output schema, the description does the necessary work of enumerating return fields and explaining the pagination flow. The schema fills in the remaining parameter-level details such as unsupported groups/private accounts. The main gap is no explicit statement about errors, rate limits, or billing, though billing is mentioned in the schema.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 100%, and every parameter already has a rich description, including handle formats/examples, language effects, and nextPageToken pagination semantics. The description's pagination sentence mostly restates the schema's nextPageToken description, so it adds little beyond the structured documentation.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description opens with 'Fetches a public Facebook page or profile by handle' and then enumerates the exact returned data (id, name, category, bio, likes, talking-about counts, followers, posts, etc.). This clearly states what the tool does and, because no other sibling tool targets Facebook, it is easy to distinguish from the Instagram/TikTok/YouTube profile tools.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description gives concrete use cases: 'enrich company or creator records, verify a brand's reach and contact details before outreach, monitor competitor pages, or build datasets of page metadata.' It does not explicitly name alternative tools or state when not to use it, but the Facebook-specific identity and public-profile restriction provide sufficient context.

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