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

With readOnlyHint already covering the safety profile, the description goes well beyond it: it enumerates every returned signal and, critically, defines the tri-state null semantics for nats_grant, nats_scoped_inbox and security_upgrade_required ('null means not known yet, never no'). That distinction between false and unknown is exactly the kind of behavior an agent cannot infer from annotations.

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 purpose and read-only nature frame the text and the field semantics follow, so it is front-loaded and every clause carries real information. It is dense and runs long as a single flowing sentence, which costs a point against an otherwise efficient structure.

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?

No output schema exists, so the description must carry the return-value burden itself — and it does, describing online state, version vs latest, upgrade availability/progress, auto-upgrade disablement, last check-in, and the three NATS security fields with their null meanings. Nothing needed to interpret a call 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?

Both parameters are fully documented in the schema (100% coverage, both optional with 'Optional when a cluster is selected'), so the schema carries the load. The description adds no guidance on cluster_id vs cluster_name precedence, but the 3 baseline applies when the schema is complete.

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?

States a specific subject and resource: the Ankra agent's own status on a cluster, with an explicit scope statement ('the twin of `ankra cluster agent status`'). That framing lets an agent distinguish it from get_cluster_status or get_cluster_details 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?

Gives three concrete triggering situations (cluster reads as offline, a feature needs a newer agent, a security upgrade notice is shown) and names the remediation sibling upgrade_cluster_agent when security_upgrade_required is true. It stops short of saying when NOT to use it (e.g. versus get_cluster_status), so it is clear context without exclusions.

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