getServerTime

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates the operation is a read-only 'Get' returning a Unix timestamp, providing the key context that this tool has no side effects. It does not mention subsecond precision or HTTP specifics, but these are not necessary for such a simple tool.

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, highly concise and front-loaded. It contains no filler and every word adds value, directly stating the tool's function and return type.

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 tool with no parameters, no output schema, and no annotations, the description completely covers the necessary information: it specifies the operation (get), the resource (server time), and the format (Unix timestamp). No additional context is required for an agent to invoke this tool correctly.

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, so this dimension is not applicable. The baseline of 4 is appropriate because the description does not need to explain parameter usage when there are none, and the schema already reflects an empty parameter set.

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 clearly states the tool's function: retrieving the current server time as a Unix timestamp. This is a specific verb-resource combination that leaves no ambiguity, and it distinguishes itself from the many sibling getter tools by focusing solely on server time.

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 description implies usage — if you need server time, use this tool — but it does not explicitly state when to use it versus alternatives. However, given that no sibling tool serves the same purpose, the implied usage is sufficient for a tool of this simplicity.

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