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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description's remaining obligation is to disclose what the response tells you — and it does: freshness timestamps, whether a refresh is currently running, and whether this is the public demo account. The demo-account and refresh-running flags are behavioral context an agent would otherwise have to discover by trial.

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?

Two sentences, front-loaded with the resource and content list, then the usage rule. The enumerated field list is dense but each item maps to a real return value, so it earns its space; a slightly leaner phrasing of "where the stored performance data stands" would tighten it further.

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 documenting return values, and it does so comprehensively — subscription state, demo flag, Ads connectivity and marketplace count, plus data coverage and refresh state. For a zero-parameter status tool with rich annotations, nothing an agent needs before calling 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 schema baseline is 4 and there is no parameter semantics to explain. Nothing in the description conflicts with the empty object 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?

Uses a specific verb ("Get") with a specific resource ("the Gloriads account context") and then enumerates the exact fields returned: subscription status, demo-account flag, Amazon Ads connection and marketplace count, and data coverage (oldest/newest day, last refresh, refresh running). This is clearly distinguishable from the reporting siblings (get_summary, get_products_report, list_campaigns) without opening any schema.

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?

"Call this first to know whether the figures are up to date" gives explicit sequencing guidance — a rare and useful routing instruction that tells the agent to run this before trusting any report output. It does not name an alternative tool or state exclusions (e.g., when not to bother calling it), so it stops short of a 5.

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