everhour_get_user_time

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

With no annotations, the description carries the full burden. It mentions pagination and date range, which are helpful, but it does not disclose the exact nature of returned time records (e.g., whether they include billable hours, task associations) or any authentication/rate-limit considerations.

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, well-structured sentence that front-loads the core purpose and includes key behavioral details (date range, pagination). Every word earns its place; no filler or redundancy.

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 tool has 5 parameters, no annotations, and no output schema, so the description must compensate. It provides the essential idea but leaves some ambiguity about the response format and exact semantics of 'time records'. For a relatively simple read operation, it is adequate but not 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?

Schema description coverage is 100%; each parameter has a clear description. The tool description adds no additional meaning beyond what the schema already provides (e.g., 'date range' and 'pagination' simply echo the from/to/page/limit parameters).

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 action ('Get'), the resource ('time records'), and the scope ('for a specific user'), distinguishing it from siblings like everhour_list_time_records. The inclusion of 'date range and pagination support' further specifies the behavior.

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 when time records for a particular user are needed, but it does not explicitly state when not to use it or mention alternatives. There is no guidance on choosing between this and similar tools like everhour_list_time_records.

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