ghl_ad_fb_pixel_upsert

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

Description adds endpoint details and OAuth scopes beyond annotations. Annotations already indicate idempotent and non-destructive, so description complements but does not repeat. Could be more explicit about behavior (e.g., idempotency), but adequate.

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 lines with no redundant information. Front-loaded with purpose, followed by technical details. Every sentence adds value.

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?

Completeness is adequate given annotations, but missing clarification of return value (no output schema). Description should mention what the API returns to help agent understand response.

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 already has 100% coverage with descriptions and examples for all parameters. Description does not add extra meaning beyond the schema, so baseline of 3 is appropriate.

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 'Upsert conversion pixel' and 'Create or update a Facebook conversion pixel configuration', specifying verb and resource. Distinguishes from sibling tool ghl_ad_fb_pixel_list which is for listing pixels.

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?

Implied usage is to create or update, but no explicit guidance on when to use versus alternatives (e.g., list tool for reading). Lacks when-not-to-use or prerequisite context.

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