teamleader_time_tracking_add

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

With no annotations provided, the description carries the full burden, but it only states 'SIDE EFFECT: creates a time log record'—essentially restating what 'add' implies. It does not disclose aspects like required fields, idempotency, permissions, or what happens on duplicate submission.

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—two short clauses totaling 13 words—and immediately communicates the core action. The side-effect note is brief and serves as a useful emphasis without padding.

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?

Despite a 100% schema coverage, the description lacks operational context: no return value, no prerequisites, no relationship to timer workflows, and no mention of required subject_id or work_type_id. Given no annotations and no output schema, this minimal description leaves the agent with significant unknowns.

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%, so all seven parameters already have clear descriptions (e.g., duration in seconds, started_at ISO 8601). The tool description adds no parameter-level detail, so the baseline score of 3 is appropriate.

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 'Add a time tracking entry' with a specific verb and resource, making the tool's function immediately obvious. It also distinguishes from sibling tools like list/update/timer_start/timer_stop by signaling a direct creation action.

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?

No guidance is provided on when to use this tool versus alternatives like timer_start, timer_stop, or time_tracking_update. The description implies 'use when you want to add an entry' but lacks explicit exclusions or alternative recommendations.

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