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

readOnlyHint=true already establishes a safe read, so the bar is low. The phrase 'no model behind it' does add real behavioral context, implying a deterministic, inexpensive poll rather than an inference call. It does not, however, say what is returned, whether it is time-sensitive, or how results should be interpreted.

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 front-loaded sentence with no waste, which is good structure. But brevity here tips into under-specification rather than crispness, so it cannot score high.

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?

With no output schema and only a readOnly hint, the description carries the full burden, and it leaves the undocumented 'detail' parameter and the meaning of the return value unexplained. An agent cannot confidently invoke this from the definition alone.

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?

Schema coverage is 0% and the single parameter 'detail' has no description. The description never references the parameter or its expected format, so it fails to compensate for the coverage gap.

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 gestures at a concept ('when to come back', 'what is due') but never states a concrete verb and resource an agent can act on. It reads as a poetic restatement of the title rather than a functional definition, and it does not distinguish itself from siblings like observe, events, or inbox.

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 one thing worth a poll with no model behind it' hints that this is a cheap, callable-anytime check, but gives no explicit when-to-use, when-not, or alternative (e.g. observe vs events). The agent must guess the triggering condition.

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