query_all_state

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

Annotations already supply the read-only and non-destructive profile, and the description's 'Query' wording is consistent with those hints. It adds the scope detail (brick plus all motor and sensor port states) but doesn't disclose output characteristics such as volume or response shape; with annotations present, this is adequate.

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 entire description is one lean, front-loaded sentence with no filler. Every word contributes to stating the operation's object and scope.

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?

For a no-required-parameter, read-only query with an output schema, the description covers the core operation. It is slightly incomplete in usage routing and parameter explanation, but the low complexity keeps the gap minor.

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 schema description coverage is 0% and the description never mentions the `format` parameter. The enum/default in the schema makes the parameter self-explanatory, but the description fails to add any meaning about how text vs json output differs.

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 uses a specific verb ('Query') and names the full resource scope ('the brick and all motor and sensor port states'). It clearly conveys an aggregate state-snapshot operation, though it doesn't explicitly distinguish itself from siblings like nxt_info.

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 explicit when-to-use or when-not-to-use guidance. The 'all' scope implies this is for a complete state snapshot rather than a per-port query, but no alternative tools are named.

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