get_page_fan_count

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the output ('integer fan count'), which is helpful, but does not cover other important aspects such as whether this is a read-only operation, potential rate limits, authentication requirements, or error conditions. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 highly concise and well-structured, consisting of three brief sentences that efficiently convey the purpose, input, and output. Every sentence earns its place by providing essential information without redundancy, making it easy to parse and understand quickly.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is reasonably complete for basic understanding. It covers the purpose and output type, but lacks details on behavioral traits and usage context. For a tool in a server with many sibling tools, more guidance on differentiation would enhance completeness, but it meets the minimum viable threshold.

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 description states 'Input: None', which aligns with the input schema having no parameters. Since there are 0 parameters and schema description coverage is 100%, the description adequately compensates by explicitly noting the lack of inputs, adding clarity beyond what the schema alone provides. This prevents confusion about expected arguments.

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 the Page's total fan/like count.' It specifies the verb ('Get') and resource ('Page's total fan/like count'), making it easy to understand what the tool does. However, it does not explicitly differentiate from sibling tools like 'get_number_of_likes' or 'get_post_reactions_like_total', which might cause confusion about scope or target.

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 no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions, such as whether it applies to a specific page or post, or how it differs from similar sibling tools like 'get_number_of_likes'. This lack of usage guidance could lead to incorrect tool selection by an AI agent.

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