Check Beat connection

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

There are no annotations, so the description must carry behavioral disclosure. 'Check' and 'list' imply read-only behavior and the description covers its two observable actions, but it does not state what happens when Beat is unreachable, whether any state changes occur, or what the response contains. That leaves moderate ambiguity for a health-check tool.

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, front-loaded with the tool's action and ending with a crisp directive. Every word earns its place; no redundant phrasing.

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 zero-parameter health-check tool with no output schema, this description is nearly complete: it states what is checked, what is listed, and when to call it. It could add expected output/error behavior, but 'Call this first' supplies the essential workflow context and there are no parameters or return annotations to reconcile.

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, so there is nothing for the description to explain. The no-parameter baseline applies, and the description correctly implies an invocation with no arguments.

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 clear verb+resource: it checks Beat's running/reachable state and lists open documents. It is clear on its own but overlaps with sibling beat_list_documents, and does not draw the distinction between merely listing documents and also validating connectivity.

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 explicit 'Call this first' gives a definite sequencing rule, establishing this as the entry-point health check before other Beat tools. It does not provide when-not-to-use guidance or name alternatives (e.g., beat_list_documents for a pure document list), so it stops short of a 5.

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