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

The annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context by disclosing that IP addresses and diagnostic parameters are removed from the result, which helps the agent set expectations about data sanitization. No contradictions with annotations.

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 that is direct and free of filler. It front-loads the core action and includes the most relevant caveat about removed fields without unnecessary elaboration.

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 simple, one-parameter read-only diagnostic with an output schema available, the description covers the essential purpose and result sanitization. Minor gaps remain around how to source printer_id and whether the printer must be in a particular state before diagnosis, but these do not substantially hinder invocation.

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 only parameter, printer_id, is not explained in the description, and the schema itself has no descriptive text beyond the title and minimum value. The description does not compensate for the low schema coverage, leaving the agent to infer how to obtain or interpret a valid printer_id.

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 identifies the action as running a read-only connection diagnostic for an existing printer, using a specific verb and resource. It is distinct from sibling tools like status retrieval or camera snapshots, and the phrase 'connection diagnostic' makes the tool's focus unambiguous.

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 intended use case is implied: an agent should call this when it needs to diagnose a printer's connection. However, the description does not explicitly state when to prefer this over alternatives, nor does it mention exclusions or prerequisites beyond 'existing printer.'

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

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable exclusions—no URL exposure, no credentials, no video stream—and clarifies the result is a single still image, which helps prevent common agent mistakes. It doesn't cover failure behavior (e.g. camera offline), but that is minor given the annotations.

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?

Two front-loaded sentences with no filler. The first sentence communicates the action and output; the second earns its place by preempting confusion about URL, credentials, and streaming.

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 simple single-parameter read-only snapshot, the description is largely complete: it states the output (an image) and the important exclusions, and annotations carry the safety profile. The main gap is not explicitly connecting printer_id to the camera selection, and there is no mention of camera-unavailable behavior, so it is not quite a 5.

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?

Schema description coverage is 0%, so the description needed to explain that printer_id selects which printer's camera is used. It never mentions the parameter or links it to the captured frame; the agent must infer the connection from the parameter name alone.

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 names a specific verb ('Capture'), a resource ('one current camera frame'), and the output form ('as an image'). It also explicitly rules out a continuous video stream, which separates it from streaming-related camera tools and makes the tool's purpose unmistakable.

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 intended use is implied: call this when you need a single still camera image. However, it does not explicitly say when to prefer it over bambuddy_get_camera_status or other printer tools, nor does it give when-not-to-use conditions.

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

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds valuable context: it checks health without opening a stream, implying no stream session is initiated. This is a meaningful behavioral trait beyond what the annotations state.

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 well-structured sentence with no redundancy. The core action is front-loaded and every word adds meaning. Perfectly sized for a simple tool.

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 only one required parameter, an output schema, and annotations covering read-only, idempotent, and non-destructive behavior, the description covers all the essential context. No additional detail is needed for an agent to invoke this correctly.

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?

Schema description coverage is 0%, but there is only one parameter, 'printer_id', which is self-explanatory by name and title. The description's mention of 'one printer camera' hints that printer_id selects the printer whose camera status is queried, but it does not explicitly describe the parameter's role or constraints.

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?

States a specific verb ('Get'), resource ('live-stream health'), and scope ('one printer camera') in a single sentence. The phrase 'without opening a stream' clearly distinguishes it from sibling tools like get_camera_snapshot, so an agent can tell them apart immediately.

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 conveys that this tool is for health checks rather than retrieving stream content, and 'without opening a stream' signals a lighter-weight alternative. It does not explicitly name a sibling or say 'use get_camera_snapshot for the actual image,' but the context is clear enough for an agent to make the right selection.

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

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

The annotations already declare read-only, idempotent, non-destructive behavior. The description adds the 'current' and 'summary' qualifiers, but does not disclose behavior for edge cases such as no active print job, offline printer, or staleness of the returned summary.

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 one front-loaded sentence with no filler. Every word contributes to identifying the operation, the resource, and the 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?

Given the low complexity, one self-explanatory parameter, read-only annotations, and an output schema, the description covers the core calling context adequately. It is only weakened by the lack of explicit routing against 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?

Schema description coverage is 0%, so the description should compensate for the single parameter. It only indirectly maps to printer_id through 'for one Bambuddy printer' and provides no guidance on how to obtain valid printer IDs or what 'current' means relative to the job.

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 ('Get'), a precise resource ('current print job summary'), and scopes it to 'one Bambuddy printer'. This clearly distinguishes it from siblings like get_printer_status, prepare_print, and list_printers.

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 guidance on when to prefer this tool over related siblings, especially get_printer_status, which could also describe current printer state. The agent must infer the intended usage from the resource name alone.

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

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context beyond those annotations by noting the snapshot is 'sanitized' and that AMS summaries are 'non-secret,' indicating that sensitive data is intentionally filtered out. No contradiction with annotations.

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, information-dense sentence. It front-loads the core action and object, then lists the relevant content categories without any filler. Every clause contributes meaning.

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 simple read-only status tool with a rich output schema, the description covers the essential scope and content areas. It does not explain how to obtain printer_id or differentiate itself from diagnostic/current-print tools, but the annotations and output schema reduce the need for additional safety or return-format detail.

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?

With 0% schema description coverage, the description needed to explain the parameter more, but it only indirectly ties printer_id to 'one Bambuddy printer.' The single parameter is fairly self-explanatory from its name and type, yet there is no guidance on where printer_id comes from or how it relates to sibling tools like bambuddy_list_printers.

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 and resource: 'Get a sanitized live status snapshot for one Bambuddy printer.' It enumerates concrete content areas (print progress, temperatures, HMS issues, non-secret AMS summaries), which makes the tool's function unambiguous and distinguishes it from broader listing or diagnostic siblings.

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 clearly implies when to use this tool: when you want a live status snapshot of a single printer, including progress, temperatures, issues, and AMS info. It does not name exclusions or explicitly contrast with siblings like bambuddy_get_current_print or bambuddy_diagnose_printer, but the scope is clear enough for an agent to select it.

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

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful behavioral context by explicitly stating that the result excludes IP addresses, serial numbers, access codes, and camera URLs, which is valuable privacy/scope information not present in annotations.

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?

Two concise sentences with no filler. The primary function is stated first, and the important exclusion detail is added in the second sentence without unnecessary verbosity.

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 simple no-parameter listing tool with strong annotations and an output schema, the description fully covers what an agent needs to know. The intentional exclusion note adds useful context without needing further elaboration.

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 has zero parameters, and the schema confirms this. The description does not need to explain parameter semantics, and none are missing. This is the appropriate baseline for a no-parameter tool.

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?

States a specific verb and resource: 'List printers configured in Bambuddy.' It also clarifies scope by naming fields that are intentionally omitted, so an agent can distinguish this from other Bambuddy listing 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?

The description makes it clear this is for listing configured printers, but it does not explicitly compare it to sibling tools like bambuddy_list_print_sources or specify when one should be preferred over another. Usage context is implied but not stated.

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

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

Annotations already signal read-only, idempotent, non-destructive behavior. The description adds meaningful domain behavior beyond that: results are recent, archived .gcode.3mf sources, and filesystem paths and archive internals are excluded. This helps set expectations about the shape of returned data.

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?

Two short sentences convey purpose, resource type, usage context, and an important exclusion. Every sentence earns its place, and the key action is 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?

The output schema and annotations reduce the burden of explaining return values and safety. However, the description leaves parameter semantics completely unaddressed and only implies when to use the tool. It is minimally viable but has clear gaps.

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?

Schema description coverage is 0% and the description does not explain limit, offset, or printer_id. The description adds no meaning beyond the raw parameter names, so an agent has to guess how these affect listing behavior. With low schema coverage, the description was responsible for compensating and did not.

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 ('List') and a well-defined resource ('recent archived .gcode.3mf print sources') tied to a clear use case ('selected for a Bambuddy queue job'). It also distinguishes itself from sibling tools like list_printers by describing a different kind of entity, and explicitly excludes filesystem paths and archive internals, further narrowing scope.

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 phrase 'can be selected for a Bambuddy queue job' gives clear context for when this tool should be used: when an agent needs an eligible print source to enqueue a job. It does not explicitly name alternatives or exclusion conditions, but the purpose is clear enough to guide selection.

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

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

Annotations already provide readOnlyHint, idempotentHint, and non-destructive behavior, and the description adds the token's five-minute/one-use nature and confirms no print is queued/startered. This enriches behavioral understanding beyond the annotations without contradiction.

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 two sentences with no fluff; the core action and output are in the first sentence, and the safety qualifier is second. Every word earns its place.

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 an output schema present and robust annotations, the description need not explain return values or safety. Required and optional parameters are apparent from the schema's required list and titles. The only notable gap is that the description does not connect specific parameters to printer/source concepts, but the schema titles partially cover that.

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?

Schema description coverage is 0%, so the description must compensate for parameter meaning, but it never mentions printer_id, archive_id, plate_id, or options. 'One archived .gcode.3mf source' vaguely hints at archive_id but does not explicitly map the noun to the parameter, leaving the agent without useful parameter semantics.

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 a specific action ('Validate one archived .gcode.3mf source') and a concrete output ('five-minute, one-use preflight token'). It also explicitly distinguishes itself from starting a print, which separates it from the sibling bambuddy_start_print.

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?

It gives clear context for when to use the tool: when you need validation and a preflight token without queueing or starting a print. It does not explicitly name an alternative tool, but the 'does not queue or start a print' statement effectively routes the agent away from start_print.

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

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

The description adds meaningful behavioral context beyond the annotations: the token is fresh and one-use, the action creates an ASAP top-priority queue item, and it can cause physical printer motion. It also reinforces the destructive/irreversible nature with a clear safety instruction, which is valuable on top of destructiveHint=true.

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 two concise sentences, front-loading the core mechanism and then immediately stating the critical safety precondition. Every sentence earns its place with no wasted words.

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?

Given the annotations and output schema, the description covers the essential safety, precondition, and behavioral context. It could be slightly more complete by pointing to a sibling tool for the preflight step, but it is not misleading and gives an agent enough to call it correctly after confirmation.

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?

With 0% schema description coverage, the description carries the burden of explaining parameters. It clarifies that preflight_token is a fresh one-use token and that the action must follow explicit user confirmation, which maps to the confirmed boolean. It does not fully detail the meaning of the boolean literal or token format, but the schema's pattern and required fields cover those constraints.

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 action (consume a one-use preflight token and create a queue item), the resource involved, and the physical consequence of printer motion. It is specific enough to distinguish this from siblings like bambuddy_prepare_print or bambuddy_list_printers.

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 gives an explicit precondition: it must only be called after the user explicitly confirms the exact preflight summary. This is strong usage guidance, though it does not name the alternative tool to use when that precondition is not met.

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