bip_get_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. 'Return' strongly implies a non-mutating read, and the field list tells the agent what data comes back, but there is no explicit statement that it has no side effects, no note on freshness or whether repeated polling is acceptable, and no cost/latency context. Useful but not a full behavioral picture for an unannotated 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?

A single sentence, front-loaded with the verb and immediately enumerating the returned data. Every clause carries information and there is no filler or repetition of the tool name.

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 must describe return values, and it does so by naming the four categories of status data. It could go further on the shape of those values (e.g., what a button-press record looks like, IP format), but for a simple status read this is largely sufficient.

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 nothing for the description to disambiguate; the baseline for a no-param tool applies. Nothing in the description misrepresents or omits parameter behavior because none exists.

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 specific verb ('Return') plus an enumerated set of returned fields: expression state, USB port, Wi-Fi IP, and recent button presses. That is far more concrete than a bare 'get status', and the read-only nature is implicit against siblings like bip_set_state and bip_speak. It stops short of explicitly naming the sibling it complements, which keeps it from a 5.

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?

Usage is only implied: an agent can infer this is the read counterpart to bip_set_state, but the description never says when to call it (e.g., before mutating state to check current conditions) or what alternatives exist. For a zero-parameter getter the inference burden is low, so a 3 rather than a 2.

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