get_websocket_status

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

No annotations are provided, so the description carries the full burden. It doesn't state whether this is read-only, what the status includes, or how it interacts with the monitoring tools. Only the bare verb 'Get' implies a read, with no permission or return-shape context.

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, efficient sentence with no preamble or filler. It is appropriately sized, though it is a bit terse and could front-load slightly more 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?

For a status tool with no annotations, no output schema, and no parameters, the description is under-specified. It doesn't explain what 'WebSocket connection and monitoring status' returns or what monitoring state it reflects, which is essential context for correct invocation in a crowded monitoring toolset.

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 takes zero parameters, so the description needn't explain them. Baseline for 0 params is 4, and there's nothing the description omits on this dimension.

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 clear verb (Get) and resource (WebSocket connection and monitoring status). It's distinguishable from siblings like start_block_monitoring or stop_all_monitoring since it's a status read, though the description doesn't explicitly differentiate from those monitoring 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?

No guidance on when to use this versus the monitoring start/stop tools or other status getters. The agent must infer context from the name alone.

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