meta_ads_pages_upload_photo

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

No annotations provided, so description fully covers behavioral traits: photo is uploaded UNPUBLISHED, requires pages_manage_posts permission and Page Access Token, notes token scope refresh needed, states mutation and non-reversibility. Comprehensive disclosure.

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?

Front-loaded with purpose, then details. Slightly lengthy but every sentence is informative. Could trim some redundancy (e.g., 'Typical flow' could be integrated). Still efficient.

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?

No output schema, but description clearly explains return value (photo_id) and its role. Covers all needed: parameters, permissions, side effects, usage flow. No gaps given tool complexity.

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 coverage is 100%, baseline 3. Description adds: mutual exclusivity of file_path/image_url, file path 30MB and format limits, account_id fallback behavior. Adds value beyond 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?

Clearly states 'Uploads a photo to a Facebook Page and returns its PAGE photo id (photo_id).' Differentiates from sibling meta_ads_images_upload_file by specifying the different id type and use case. Specific verb 'uploads', resource 'photo to Facebook Page', scope clearly defined.

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 explicit use case: needed for Instant Form cover_photo_id. Contrasts with meta_ads_images_upload_file. Describes typical flow. Lacks explicit 'when not to use' but context is clear.

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