resolve_page_identity

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

Describes the resolution process (ladder, fallback) and role of account_id. With no annotations, the description does not disclose read-only nature, permissions, rate limits, or failure modes, leaving some behavioral gaps.

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?

Very concise: 4 sentences front-loaded with purpose, then method, then parameter explanations. No wasted words.

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?

Adequate but missing output format details. No output schema exists, so the description should specify what 'page details' and 'Instagram business account' include. Also no mention of error conditions.

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 has 0% description coverage, but the description adds meaningful context: page_id is the Facebook Page ID, account_id is optional and improves IG resolution. This compensates well for the lack of schema descriptions.

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?

Clearly states the tool resolves full identity for a Facebook Page including Instagram business account details. The verb 'resolve' and resource 'page identity' are specific, and it distinguishes from sibling tools like get_account_pages or get_instagram_identities.

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?

Provides context on when to use (to get full identity including Instagram) and mentions the 3-step resolution ladder and fallback behavior. However, it does not explicitly exclude alternatives or tell when not to use this tool over siblings.

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