get_n_queued_items

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

With no annotations, the description carries the burden and discloses return value range (0–32), the meaning of the threshold, and the broadcast caveat that 'all' receives no response. It does not explicitly state read-only behavior, but 'Get' and 'Status & Monitoring' imply it.

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?

Front-loads the core function and practical warning, then presents return value and parameter details. Slightly redundant in mentioning queue capacity twice, but every sentence contributes useful 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?

For a one-parameter read-only status tool with no output schema, the description provides the return shape, range, parameter syntax, and usage guidance. An agent has enough information to invoke it correctly in the context of the observable sibling tools.

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 motor parameter is fully described beyond the bare schema: alias number, 16-hex-digit unique ID, special 'all' value, and the no-response consequence for broadcasts. This thoroughly compensates for 0% schema description coverage.

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?

Clearly identifies the operation ('Get the number of items') and the specific resource ('movement queue'), plus the firmware group 'Status & Monitoring'. The queue-specific focus distinguishes it from the many movement and status sibling 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?

Gives actionable guidance: check the queue size before queueing movements, and only add more items if the count is below 32. It does not explicitly name alternative tools or exclusions, but the usage context is clear.

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