status

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety and locality are covered. The description contributes the notion that it surfaces backlog and cross-machine replication state, but says nothing about output shape, cost, or whether it is a point-in-time snapshot — a 3 given the annotation coverage.

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?

It is a single short sentence with no padding, so length is fine. However, it reads as an incomplete fragment ('The summary backlog and...') rather than a front-loaded statement of purpose, costing clarity per word.

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, annotation-backed read tool the bar is modest, and the description names the two data domains returned. Still, with no output schema and no description of the response structure or when the tool is the right choice, an agent lacks enough to invoke it confidently at the right moment.

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 there is nothing for the description to disambiguate; baseline 4 applies. No parameter-related guidance is needed or missing.

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 identifies the content reported (summary backlog and replication state between machines), which is a resource-level statement. But it is a noun phrase with no verb and no framing of what 'status' actually returns or does, and it does nothing to distinguish itself from siblings like 'view' or 'thread'.

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 indication of when to call this versus the many siblings (view, search, thread, read_message, compact_*). Nothing about preconditions, frequency, or typical triggering situations; the agent must infer usage entirely.

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