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

Annotations already declare the tool read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds a useful non-obvious behavioral caveat—'empty observations do not imply uptime'—which helps the agent interpret sparse or empty results correctly. That extra semantic warning is meaningful and not redundant with annotations.

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?

The description is a single sentence with no filler. It front-loads the action and resource before adding the interpretive caveat, making it easy to parse quickly.

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-rich read tool, the description covers the main semantic risk with the uptime caveat and identifies what the tool reads. It does not describe output format, but no output schema exists and the annotations already cover the operation's safety profile.

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 has zero parameters and an empty input schema, so there is nothing the description must explain about argument meaning. The baseline of 4 for no-parameter tools applies, and the description appropriately spends no space on parameters.

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 uses a specific verb ('Read and a clearly identified resource ('observed execution/MCP metrics and configuration'), which sets it apart from execution-oriented siblings like xguard_execute. It does not explicitly name alternative tools, but the resource scope is distinct enough that an agent can recognize its purpose.

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?

There is no explicit guidance about when to use this tool versus sibling tools such as xguard_discover or xguard_get_result. The caveat about empty observations gives interpretation guidance after the fact, but it does not tell the agent when this tool is the right choice.

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