get_account_pages

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 states what data is retrieved but lacks critical details: whether this is a read-only operation, if it requires specific permissions, rate limits, pagination behavior, or error conditions. For a data retrieval tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. It directly states what the tool does ('Get Facebook pages... and their Instagram business accounts'), earning its place by clearly defining scope. There is no redundancy or fluff.

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 complexity (retrieving connected social media accounts), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the output includes (e.g., page IDs, names, Instagram account details), potential errors, or dependencies like authentication. For a tool in a server with many siblings, more context is needed to use it effectively.

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 tool has 0 parameters, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, but it correctly implies no inputs are required. Baseline for 0 parameters is 4, as the description aligns with the empty schema.

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: retrieving Facebook pages and their connected Instagram business accounts. It uses specific verbs ('Get') and resources ('Facebook pages', 'Instagram business accounts'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_profile_info' or 'business_discovery', which might also retrieve account-related data.

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 doesn't mention prerequisites (e.g., authentication state), exclusions, or compare it to siblings like 'get_profile_info' for general account data or 'business_discovery' for business-specific insights. Usage is implied only by the tool's name and description.

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