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

With annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) already covering the safety profile, the description adds real context: the ticket is private and expiring, it performs 'no binding, replacement or ad changes', and there is no auto-polling. That clarifies the side-effect footprint beyond the annotations.

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?

Packed into a single semicolon-delimited run-on sentence. It is front-loaded with the purpose and free of filler, but the telegraphic style and lack of sentence boundaries make it harder to parse than it needs to be.

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?

An output schema exists, so return values need not be explained, and the begin-then-check workflow is covered. However, with 0% schema description coverage the description should document the two inputs, which it does not, leaving the parameters underspecified.

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% for both parameters. The description never explains what 'channel' values are valid or what 'connection_context' (pattern mctx_v1_...) represents; the only token mentioned, 'connect_id', is a parameter of the sibling check tool, not of this one. It fails to compensate for the coverage gap.

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 specific verb and resource: 'Create a private expiring authorization ticket/receipt.' It implies a channel-scoped authorization flow (vs the sibling setup_begin_facebook_connect), but never names that sibling or explicitly contrasts with it, so differentiation is inferential rather than stated.

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?

Gives a clear operational sequence: user consents in the browser at authorize_url, then call setup_check_channel_connect once with connect_id, and 'no auto-poll'. This is strong when-to-use guidance and names the follow-up tool, though it does not contrast with other setup_* alternatives.

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