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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description still adds genuine context the annotations do not encode: it is public, needs no token, is live/non-cached, and its payload includes separate account and anonymous-demo limits plus polling guidance. It does not say how current the 'live' data is or whether it can be stale, which matters for a pre-flight check.

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?

Three short sentences with no filler, and the most load-bearing prior ('no token required') is near the front. The middle sentence is a dense compressed list ('separate account and anonymous-demo limits and polling guidance') that takes a second read, but nothing is redundant.

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 and no parameters, the description carries the burden of telling the agent what comes back, and it does list the payload categories. It is missing only refresh/caching semantics and any hint that the response shape is structured, but for a zero-arg read-only status probe it is substantively complete.

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 already leaves nothing to misinterpret and the baseline expectation is met without description support. The description mentions 'separate account and anonymous-demo limits', which implicitly explains why no account identifier is needed, but it adds no parameter-level meaning because none exists.

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 enumerates what the caller gets back: live availability, model catalog, account vs anonymous-demo limits, and polling guidance. That is more specific than the title alone, though it is written as a noun-phrase inventory with no explicit verb and never distinguishes itself from siblings like get_capability_catalog or get_compute_status, which sound like they could overlap with the 'model catalog' and availability content.

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?

It gives a real trigger condition — 'Check before submitting; an offline GPU cannot execute work' — which tells the agent when to call it and why it matters. It also notes 'No token required', removing an auth precondition. It stops short of naming a sibling or stating exclusions (e.g. when to prefer get_compute_status), so it is clear context without full routing guidance.

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