Discover local Rust clients

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real trust-model context beyond that: capabilities are signed and short-lived, device names are not attestation, unsupported older clients are not guessed, and no compilation happens server-side. This is genuinely useful behavioral disclosure, though it leaves the return shape unstated.

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?

Four short sentences with the core action front-loaded and no filler. Some phrasing is terse to the point of being cryptic—"compare fingerprints in Share" assumes an undefined surface—but the text is compact and each sentence contributes context.

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, the description should say more about what a caller receives—whether it is a list of clients, a capability set, or grants. It covers the trust and safety model well for a zero-argument read tool, but the discoverability contract is left implicit.

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 there is no parameter meaning for the description to carry; the baseline for a parameterless schema applies. The description does not introduce any spurious argument semantics.

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 gives a verb ("Read") and a resource ("signed, short-lived device/browser capabilities and explicit grants"), but it never plainly states that this tool enumerates or discovers the local Rust clients named in the title. An agent reading only the description could mistake it for a credential-reading operation rather than a client-discovery listing.

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?

There is no statement of when to call this versus siblings such as crabrix_status, crabrix_runtime_start, or crabrix_runtime_request. "Compare fingerprints in Share" hints at a workflow but does not define a selection condition or exclusion.

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