diagnose_pixel_on_site

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

No annotations provided; description discloses that it uses a headless browser and checks specific items, but does not state if it's destructive, error handling, or what happens on failure. Minimal behavioral context.

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?

Three sentences plus Arg list, all essential information, no fluff. Front-loaded with main purpose.

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; description mentions checks but not what is returned. For a diagnostic tool, more detail on output format or success/failure indicators would improve completeness.

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% coverage; description adds brief explanations for url and pixel_id (e.g., 'Website URL to check'), providing some value but not detailed formatting or usage beyond the 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?

Description clearly states it diagnoses pixel installation on a website via headless browser, listing specific checks. It distinguishes from siblings like get_pixel_info, run_tracking_diagnostic, etc.

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?

Mentions requirement for Puppeteer but gives no explicit guidance on when to use this tool vs alternatives. No exclusions or comparisons provided.

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