timeiq_time_create

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

No annotations are provided, so the description carries full burden. It only states the purpose and a parameter constraint, but fails to disclose side effects (e.g., does it check for overlaps? Does it support multiple entries per day?), required permissions, or error handling.

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 sentence, making it concise but lacking structure. Given the tool's complexity (11 parameters), more information is needed. The sentence earns its place but doesn't cover enough.

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?

With no output schema, no annotations, and a complex set of parameters, the description is incomplete. It omits return values, error scenarios, and parameter formatting details, leaving significant gaps for the agent.

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 0% (11 parameters, none described in schema). The description only explains the mutual exclusion between start_time/end_time and duration, ignoring other parameters like date, project_id, notes, is_billable, service_id, timeZone, dry_run, requesting_slack_id.

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 'Create a new time entry' with a specific verb and resource. It distinguishes from siblings like timeiq_time_update or timeiq_time_batch by mentioning the constraint of providing either start_time/end_time pair or duration.

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 only provides the mutual exclusion constraint for parameters but offers no guidance on when to use this tool versus siblings like timeiq_time_create_overbook or timeiq_timer_start. No when-not-to-use or alternative tool references.

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