gta-reset-times

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

No annotations are provided, so the description carries the full burden. It states 'Pure computation, always available', which indicates no side effects, permissions, or rate limits. This is accurate but minimal. There is no contradiction between description and 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, concise sentence that conveys the essential information: what the tool does and its nature. Every word earns its place. No unnecessary phrasing or repetition.

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?

The description is adequate for a simple tool with no parameters and a clear purpose. However, it does not specify the output format (e.g., whether it returns seconds, formatted time, or a JSON object). Given that there is no output schema, the description should provide more detail on return values to be fully complete.

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, and schema description coverage is 100% automatically. With no parameters, the description does not need to add parameter meaning. The baseline score of 4 is appropriate because there is nothing to add.

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 provides 'Time remaining until the GTA Online daily reset (06:00 UTC) and weekly reset (Thursday 07:00 UTC)'. It identifies the resource ('reset times') and the action ('time remaining'). However, it does not explicitly distinguish itself from sibling tools, many of which are unrelated but some might also deal with 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 by stating 'Pure computation, always available', suggesting it is a simple, non-destructive query that can be used anytime. However, it does not provide explicit guidance on when to use versus sibling tools or any exclusions. The context is clear but minimal.

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