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

The annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable behavioral semantics beyond this, such as defining each bucket (e.g., 'awaiting_bed_clear' means a print finished but bed not cleared) and explicitly noting that 'Counts overlap intentionally' (e.g., a printer can be in 'online' + 'printing' + 'ai_running'). This transparency helps the agent understand the nuanced state model.

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 description is a single paragraph that is quite long due to the need to define many buckets. However, every sentence serves a purpose: the opening sentence states the primary use, the middle lists all buckets, and the closing sentence clarifies the overlap semantics. It is front-loaded with the core purpose. It earns its length given the tool's complexity, though it could be broken into a list for readability.

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 present, the description must explain what the tool returns, and it does so thoroughly. It specifies a top-level total and a {count, printers:[{id,name}]} structure per bucket, and enumerates every bucket with appropriate definitions. It also explains the intentional overlap, making the return semantics fully self-contained.

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 input schema has zero parameters (properties: {}), so schema coverage is 100% trivially. There are no parameters to explain. The description doesn't discuss parameters, which is appropriate. Per the rubric, a baseline of 4 is given for 0-param tools, and the description uses this opportunity to explain the output structure instead, which is helpful.

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 clearly states the tool's function: 'One-shot summary of farm-wide printer state.' It uses a specific verb ('get') and resource ('farm overview'), and distinguishes itself from the sibling tool 'list_printers' by explicitly saying 'Use this (NOT list_printers)'. The list of buckets further clarifies what the summary includes.

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?

The description explicitly tells when to use the tool: 'when the user asks "how many printers are printing/idle/awaiting bed clear/etc." or "what is the state of the farm"'. It also names the alternative (list_printers) and explains why NOT to use it for these queries. This is clear usage guidance.

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