get_busy_snapshot

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

With no annotations provided, the description carries the full burden. It discloses that the tool queries a GET endpoint via BusyApi.get_busy_snapshot(), implying a read-only operation, and thoroughly explains the return structure for all snapshot variants. It lacks explicit mention of side effects, but the GET method strongly implies none.

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 well-structured, starting with a one-sentence summary, followed by API details, a nested list of return variants, and a use case. Every sentence provides necessary value, especially given the lack of an output schema.

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 description is complete for a simple getter: it explains what it does, how it works, the exact return shape for every variant, and when to use it. There is no output schema, so the detailed return documentation is essential and fully provided.

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 schema coverage is 100%, so the schema requires no explanation. The description adds meaning by detailing the return types and use case, which is appropriate for a parameterless 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?

The description clearly states the tool retrieves the current BUSY timer snapshot from the Busy Bar device, using a specific verb and resource. It distinguishes from siblings by focusing on the BUSY snapshot, which no other sibling tool addresses.

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 provides a clear use case: checking the active BUSY profile and remaining time before scheduling operations. It does not explicitly mention when not to use it or name alternatives, but the context is clear for a simple getter tool.

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