get_my_clock

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

The description does not disclose any behavioral aspects such as side effects (read-only vs. mutating), authentication requirements, rate limits, or error conditions. Since no annotations are provided, the description carries the full burden, and 'Get' alone does not explicitly confirm safety.

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 with no unnecessary words. It is front-loaded with the action and resource, making it immediately understandable.

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 provides sufficient context for a simple getter: it identifies the resource (currently running clock) and the scope (authenticated user). It does not specify the return format, but given the lack of an output schema, this is acceptable for a basic retrieval.

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 no parameters, and the description adds no additional meaning beyond the empty schema. Since schema coverage is effectively 100% (nothing to cover), the baseline of 3 applies, and the description offers no extra semantic detail.

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 a specific action ('Get') and resource ('currently running clock') for the authenticated user. It effectively distinguishes itself from sibling tools like start_my_clock and get_my_time_entries by focusing on retrieving the active clock.

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 on when to use this tool versus alternatives. While the name and description imply it is for retrieving the running clock, it does not state conditions like 'use this when you need the current active clock' or contrast with get_my_time_entries.

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