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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety and idempotency are covered. The description adds non-obvious behavioral context: it is a reporting/description call, not an authorization gate, and errors from other tools should be surfaced rather than pre-empted. It does not discuss return format, but no output schema exists, so a small gap remains.

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 sentences, front-loaded with the purpose, then the when-to-use, then the anti-pattern exclusion. No filler, no repetition of schema or annotation content.

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 parameterless read-only description tool with no output schema, the description delivers purpose, when-to-use, when-not-to-use, and the key anti-pattern. 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?

Schema coverage is 100%, so both parameters (context, conversation_id) are already fully documented, and the description correctly does not restate them. The conversation_id semantics, including the omit-on-first-call rule, live in the schema and are not repeated, so no extra value or harm is added here. Baseline would be 3, but the usage guidance around not using this tool as a pre-check effectively scopes the call, nudging it to 4.

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 (Describe) and resource (the hub), and enumerates exactly what is returned: the hub, the account's membership role, and Cycle capabilities in it. It is clearly distinguishable from siblings like list_servers or get_jobs, which return different resources.

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 an explicit when-to-use trigger ('only when the user asks about their hub, account, role, or permissions') and an explicit when-not-to-use rule ('Do not call it to pre-check whether another tool is allowed: call that tool directly'). That is a direct routing instruction against a plausible misuse.

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