get_capabilities

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

No annotations are supplied, so the description carries the full burden. It discloses that output is grouped by area, but says nothing about volume of output, whether it is cached/static, or whether the bridge connection must be validated first. Adequate but thin for a no-annotation tool.

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 short sentences, purpose first and usage hint second, with no filler. Nothing could be removed without losing information.

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?

An output schema exists, so return values need not be explained. The description need only cover purpose and usage, which it does; the only gap is behavioral context (output size/cost) that annotations would normally carry.

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, which establishes the baseline of 4. Schema coverage is 100% and there is nothing to disambiguate, so no further parameter discussion is needed.

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 verb and resource ('List every command the connected bridge supports') and adds the grouping behavior. Among a large sibling set it doesn't name or contrast any specific alternative, so the differentiation relies on the reader inferring that a meta-discovery tool is distinct from the domain-specific tools.

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?

'Use this to discover functionality beyond the named tools' gives clear context for when to reach for it, which is genuinely useful in a large toolset. No explicit when-not or named alternatives are provided, but the discovery framing is sufficient to route most agents correctly.

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