server_stats

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

No annotations are provided, so the description carries full burden. It discloses that started_at is set at server start and uptime_seconds is elapsed seconds. As a read-only operation with no side effects, the description is transparent enough for safe invocation.

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?

Three sentences, each essential: first states core purpose, second provides usage examples, third clarifies the meaning of returned fields. No fluff, front-loaded.

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?

Given zero parameters and presence of an output schema (mentioned in context signals), the description adequately explains the return values (started_at, uptime_seconds) and their meaning. No additional information is needed for a tool of this simplicity.

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, with 100% schema description coverage. Per guidelines, 0 parameters yields a baseline of 4. The description does not need to add parameter information as none exist.

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?

Description clearly states it returns server process start time and uptime, with specific examples ('how fast did model-radar come up'). The verb 'Return' and resource 'server process started/uptime' are specific, and no sibling tool duplicates this function.

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?

Explicit usage directions are given ('Use to answer questions like...'), providing clear context for when to invoke. However, it does not mention when not to use or list alternatives, but given the uniqueness of the tool and simplicity, this is sufficient.

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