Test the Meta connection

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

With no annotations, the description carries the burden and does well: it discloses the exact destination (Meta Events Manager test events), that it relies on already-saved workspace pixel/token/test_event_code, and that production data is untouched. It omits what happens when credentials are missing or why a result would be 'skipped'.

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 short sentences, each doing distinct work: what is sent, what comes back, and what is not affected. The key safety fact is stated last but not buried.

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?

With no parameters and no output schema, the description must cover the return shape, and it does ('sent/skipped/failed with Meta's error and a hint'). The meaning of 'skipped' — presumably missing or invalid workspace credentials — is left for the agent to infer.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly notes that configuration comes from the workspace's saved Meta pixel, token and test_event_code rather than from inputs, which is the useful fact for an agent.

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?

States a concrete verb and resource ('Send one synthetic Lead to Meta Events Manager → Test events') plus the credentials it uses, so the action is unambiguous. The word 'synthetic' and 'Does not affect production data' implicitly separate it from track_event, but no sibling is named explicitly.

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 framing ('Test events', 'synthetic Lead', 'does not affect production data') makes the intended use — verifying the Meta connection without touching production — clear. It stops short of explicitly saying 'run this before track_event' or naming what to use instead when validating real payloads.

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