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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds that the operation evaluates each supplied ID individually and is account-scoped, but it does not disclose result shape, partial-failure behavior, or rate/permission concerns.

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 a single front-loaded sentence with no filler. It communicates the core check and the per-ID semantics efficiently.

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?

For a one-parameter, read-only, idempotent lookup with rich annotations and no output schema, the description gives enough context to invoke it correctly. The main minor gap is that it does not describe the per-ID result semantics explicitly.

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 effectively low for the array parameter, though the item schema documents that it is a Meta advertiser page ID kept as a string. The description echoes the string ID expectation but does not add format, limit, or error-handling detail 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?

The description states a specific verb ('check') and resource ('whether each string Meta page ID is actively tracked by your account'), which is clear and distinct from sibling mutation tool track_brand. It does not explicitly contrast with list_tracked_brands or search_tracked_brands, so sibling differentiation is only implicit.

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: check known page IDs for tracking status. The description does not state when to prefer this over list_tracked_brands or search_tracked_brands, nor does it call out that track_brand is the mutation alternative.

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