validate_catalog_connections

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

With no annotations, the description carries the burden. It implies a read-only health check (validate, not mutate) but does not disclose authorization needs, rate limits, side effects, or what happens on failure. Adding details about return format or error handling would improve transparency.

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 concise: one-line summary, a brief context sentence, and a bulleted Args list. No filler, front-loaded with purpose. Every sentence earns its place.

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?

The tool has 4 params and no output schema. The description explains purpose and params but does not describe the return value (e.g., what the health assessment outputs). For a diagnostic tool, omitting output expectation reduces 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 description coverage is 0%, so the description's Args section is essential. It explains each parameter's role (catalog_id required, other optional for specific link verification), adding meaning beyond the schema's type info. Could include formats or examples for higher score.

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 verb 'validate' and specific resource 'catalog-pixel-account-page connection chain', and explains the diagnostic health assessment purpose. It distinguishes from siblings like check_token_status and diagnose_pixel_on_site by focusing on the full catalog chain.

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 context that the tool is for DPA setup/debugging ('For DPA to work'), but does not explicitly state when to use it vs alternatives like diagnose_pixel_on_site or run_tracking_diagnostic, nor does it mention when not to use it.

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