everhour_add_time_to_task

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

There are no annotations, so the description bears the full burden of behavioral disclosure. It merely states the action and endpoint without revealing side effects, permission requirements, idempotency, or response behavior. The tool performs a write operation, but no details are given.

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 that immediately states the action and endpoint. It is front-loaded with the verb and target, containing 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 description is minimal and lacks critical context. With no annotations or output schema, the tool's behavior, return value, and relationship to sibling tools remain unexplained. It covers the basic purpose but leaves significant gaps for a time-tracking API.

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 input schema provides 100% coverage with descriptions for all parameters, including time format. The description adds no extra parameter context beyond mentioning the endpoint, so the baseline 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 the tool adds time to a specific task and even names the API endpoint. It includes a specific verb and resource, making the core purpose obvious. However, it does not explicitly distinguish this from sibling tools like create_time_record or update_task_time.

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. The description does not mention any prerequisites, exclusions, or differentiation from similar time-tracking tools such as everhour_create_time_record or everhour_update_task_time.

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