get_command_journal

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

With no annotations, the description carries the full burden and excels: it explains that entries mean messages left this machine, not that the desk received or acted on them, and warns about manual fader movements that the server wouldn't know. This reveals crucial behavioral limitations beyond a simple 'returns' statement.

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 front-loaded with the core purpose, then uses two further paragraphs that each add essential caveats about data interpretation and usage. Every sentence earns its place without being wordy, and the structure is logical (function, meaning, guidance).

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?

Despite being a zero-parameter tool with an output schema, the description provides all necessary context: what the data represents, its limitations, and when to use it. It sufficiently covers the semantics of the returned journal without needing to detail return fields.

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, so the empty schema already provides complete coverage. The description appropriately avoids inventing parameters, and no further parameter-level explanation is needed, matching the baseline 4 for parameterless tools.

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 that the tool returns this server's sent console messages, using a specific verb ('returns') and resource ('what this server has sent to the console'). It actively distinguishes this from the console's actual state, setting it apart from sibling tools that query or modify state.

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 explicit positive guidance ('Use it to retrace what you did') and negative guidance ('never to answer what the rig is doing'). It also clarifies that entries do not imply receipt or action, which is a clear exclusionary instruction.

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