facebook_page

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that it 'Fetches public data,' indicating a read-only operation, and notes the source ('About tab') for contact details. It does not discuss rate limits or error cases, but for a simple public-data lookup this is adequate.

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 concise, consisting of two sentences. The primary action is front-loaded in the first word, and every subsequent clause adds valuable detail about input or returned fields, with no redundant wording.

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?

For a one-parameter tool with no output schema, the description adequately covers the returned data and input formats. It enumerates the data fields and indicates the data source, but does not mention potential edge cases (e.g., missing fields or invalid IDs), which is a minor gap for an otherwise complete description.

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 already provides 100% coverage for the single parameter, describing the accepted forms (vanity name, handle, profile.php id, or full URL). The description restates the same input options without adding new semantic meaning, so the baseline of 3 is appropriate.

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's purpose: 'Get Facebook page details.' It uses a specific verb with a specific resource, and enumerates the data fields returned (name, follower counts, category, contact details), making it easy to distinguish from sibling tools like facebook_group or facebook_marketplace.

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 provides clear context about when to use this tool—whenever a Facebook Page's public details are needed. It explains the accepted input formats (page ID, vanity name, or URL), though it does not explicitly mention alternatives or exclusions, which keeps it just short of a 5.

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