add_my_time_entry

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

No annotations are provided, so the description carries the full burden of transparency. It states the action ('Add') and the target ('a manual time entry'), but does not disclose any potential side effects, error conditions, or details about the created record's association. The behavior is minimally transparent but lacks deeper disclosure.

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 extremely concise, with no redundant information. Each parameter is listed briefly and clearly. The entire description is compact and efficiently communicates the necessary details.

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 covers the core purpose and all parameters. It does not explicitly mention return values or possible errors, but given the simplicity of a create operation and the lack of an output schema, this is a minor gap. Overall, it provides enough context for an agent to invoke the 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 parameter descriptions in the tool description add meaningful context beyond the raw schema types. It clarifies the roles of customers_id, services_id, time_since, time_until, billable, and marks projects_id and text as optional. It also provides examples for time format. This exceeds the schema's bare type information.

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: 'Add a manual time entry for the authenticated user.' It uses a specific verb (add) and resource (time entry), and it is distinct from sibling tools like start_my_clock or add_my_vacation which perform different actions.

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 does not explicitly mention when to use this tool versus alternatives. It implies usage for manual time entry logging, but does not state conditions or contrast with other tools like start_my_clock or add_my_vacation. Thus the usage guidance is implied rather than explicit.

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