Get Page Info

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

Annotations already declare readOnlyHint=true, and the description adds behavioral context: it 'fetches the public (or logged-in) profile page and parses ... from embedded page data,' indicating a scraping mechanism and possible dependence on login status. This goes beyond the annotations and helps the agent understand what actually happens.

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 two sentences, with the primary purpose in the first sentence and details in the second. No filler or redundant information; every word adds value. It is optimally concise and front-loaded.

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 simple tool with one parameter, an output schema, and read-only annotations, the description covers the essential purpose and data extracted. It does not describe return values, but the output schema likely does. The only minor gap is lack of mention of rate limits or login requirements, but the 'logged-in' hint and annotations provide enough for this complexity level.

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 description coverage is 100%, with the username parameter already explained as 'Page or profile username (e.g. 'cocacola')'. The description adds only the phrase 'by username,' which adds no new semantics. The schema carries the burden, so a baseline score of 3 is warranted.

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 'Get Facebook Page/profile details by username' with a specific verb and resource, then lists the exact data extracted (name, id, bio, follower counts). This distinguishes it from siblings like get_me (own profile), search_pages (search), or get_page_posts (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?

The description implies usage when you have a username and want profile details, providing clear context. However, it does not explicitly mention when not to use it or name alternatives (e.g., use get_me for the logged-in account, search_pages for searching). Still, the 'by username' phrasing gives enough guidance for typical use.

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