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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them by decoding the edge states (connected false = Channable not connected, no feeds = nothing linked, google null = Merchant Center not connected) and detailing the actual return contents. This is exactly the behavioral context annotations cannot carry.

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?

It is long and dense with a sprawling first sentence, but it is front-loaded with the core purpose and each clause (return contents, usage triggers, edge-state semantics) adds distinct value. Slightly heavier than ideal but not padded.

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?

There is no output schema, so the description carries the full burden of explaining return values, which it does comprehensively (per-feed coverage, omitted stocked products, conflicts, brand values, Google approval/disapproval and blocking issues). Nothing an agent needs to call it 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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate beyond the implicit global scope of the read.

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?

Names a specific resource (the brand's linked Channable channel feeds / catalogues sent to Meta, Google Shopping and marketplaces) read against Shopify, and enumerates exactly what it returns. It is clearly distinguishable from siblings like get_channels or get_product_performance because the scope (feed coverage, conflicts, Google verdicts) is stated 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 'Use for any question about channel catalogues, product feeds, Channable, Google Shopping disapprovals...' sentence gives strong, concrete when-to-use triggers. It does not name an alternative sibling or state exclusions/when-not, so it stops short of the top band.

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