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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description's job is to add context, and it does: results are ordered newest first and each row reports where the ad went. It also discloses a non-obvious visibility rule (another Apogee user's transfers appear when the destination account is yours), which an agent could not infer from structured fields.

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 opening line is front-loaded and answers 'what and where' immediately. The second sentence is information-dense but slightly redundant, restating 'already copied' as 'already bridged' and packing a visibility caveat into a trailing clause; a small trim would improve it.

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 output schema, the description carries the burden of explaining returns and does so by enumerating the fields per row and the sort order. It also clarifies data scope across users. Minor gaps remain around pagination behavior and how source_platform narrows results, but nothing essential to calling the tool correctly is missing.

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 100%, so limit, source_platform (with its enum), and source_ad_account_id are already documented in the schema. The description implies the source-account scoping but adds no format, default, or filtering detail beyond what the schema supplies, so the baseline 3 applies.

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 gives a specific verb and resource ('ads already bridged from a source ad account'), plus the shape of each result row (source ad plus platform, ad account, ad, ad set) and ordering (newest first). That is far more than a restatement of the title. It does not explicitly name how it differs from nearby siblings such as list_ads, get_ads, or bridge_transfer_status, so it stops short of a 5.

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?

Usage is implied by the framing ('the app's Bridged tab', 'which ads were already copied'), so an agent can infer this is the tool for viewing existing cross-platform copies. However, there is no explicit when-to-use statement, no exclusion of alternatives, and no mention of when to prefer bridge_transfer_status or get_bridge_stats instead.

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