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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral detail the annotations do not carry: that it reveals the actor name writes are attributed to and the current root, which matters for later write calls.

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 sentences, no filler, with the invocation trigger front-loaded and the secondary return content ('Also returns the current root') placed last. Every clause carries information.

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 read-only, zero-required-parameter tool with full schema coverage, the description enumerates the four things the caller learns (health, facts presence, actor, root), which is the right substitute for a missing output schema. It stops short of describing return format or any error/offline signaling, which would complete it.

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?

One optional parameter with 100% schema description coverage, which already explains workspace semantics and the default behavior. The description adds no workspace-format or resolution detail beyond that, so the schema does the heavy lifting and the baseline of 3 applies.

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?

Concrete verb (check) plus exactly what is checked: store reachability/health, whether any facts exist, the actor name attributed to writes, and the current root. No sibling tool (list_apps, get_entity, record_fact, etc.) overlaps with this diagnostic view, so the agent can separate it immediately.

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?

Opens with an explicit trigger phrase ('Use to check that the store is reachable and healthy...'), giving clear context for invocation. It does not state when not to use it or name an alternative, but there is no competing status/diagnostic sibling to route away from.

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