status

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

No annotations are supplied, so the description carries the full burden, yet it never states that this is a read-only, side-effect-free query, whether an unavailable BRouter instance is reported as an error or as a value, or what the reachability/coverage fields mean. Listing the reported facets is a start but leaves the behavioral profile thin.

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?

It is a single compact sentence with zero padding, which is good, but as a sentence fragment without a subject or verb it reads as a field list rather than a definition, and the most important information (what the tool returns/why to call it) is not front-loaded.

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-value detail is legitimately omitted, and with zero parameters the call mechanics are trivial. Still, for a status/health tool it would help to say it reports the state of the configured BRouter instance and is the natural first call in the workflow, which is absent.

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 fully covers the call signature; the description adds nothing to misinterpret and nothing is missing on the parameter side.

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 the domains reported (reachability, region, weight set, flow index size, DEM coverage), which tells an agent what information is surfaced, but it is a noun phrase with no verb, so the action (return current BRouter server/segment state) is only inferred from the name 'status'. It also never distinguishes itself from siblings like start_brouter or list_presets.

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?

No when-to-use guidance is given: nothing says this is the pre-flight/health check before calling plan_route or route_details, and no alternatives or exclusions are named. The agent must infer applicability from the tool name alone.

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