grocy_system_time

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds the concrete endpoint and the fact that the offset is optional, but says nothing about the returned time format or timezone, which matters for interpreting an offset.

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 short fragments, front-loaded with the resource, with zero padding. The endpoint path is arguably redundant but aids traceability; the telegraphic style leaves a bit of ambiguity in the third fragment.

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-required-parameter read tool with full schema coverage and annotations carrying the safety profile, this is nearly complete. The only meaningful omission is what the response looks like (unix epoch vs ISO string, timezone), which the agent would need to apply the offset 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?

Schema coverage is 100% and the single parameter has its own description ('Offset of the timestamp in seconds') plus min/max bounds. The description's 'Optional offset seconds' only restates optionality, which the schema already encodes via zero required parameters, so the baseline 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?

States a specific resource and verb-equivalent: it returns the current Grocy server time, and it even names the backing endpoint (GET /api/system/time). It does not explicitly differentiate itself from the nearby grocy_system_db_changed_time or grocy_system_info siblings, so it stops short of a 5.

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 statement of when to call this versus grocy_system_db_changed_time or grocy_system_info, nor any note about prerequisites such as authentication. Usage is only inferable from the phrase 'Current Grocy server time'.

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