log_time

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

Annotations already indicate this is a write operation (readOnlyHint=false). Description adds that it logs past entries, but does not further disclose behavioral traits (e.g., whether it overwrites existing entries, permission requirements). Acceptable bar with annotations present.

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?

Two sentences, front-loaded with purpose, efficient in wording, no extraneous information.

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?

Given 6 parameters with conditional rules and no output schema, the description covers the essential usage logic. Lacks mention of return value or error handling, but these are not critical for selection/invocation.

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 covers all 6 parameters with descriptions. Description adds value by explaining the conditional relationship between duration and startTime/endTime, and clarifies that duration is relative to now, which is not in schema.

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?

Description clearly states 'Log a manual (past) time entry,' specifying the action (log), resource (time entry), and context (past). Distinguishes from sibling tools like start_timer/stop_timer which handle active timers.

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?

Provides clear guidance on the conditional use of duration vs. startTime/endTime. However, does not explicitly contrast with sibling tools (e.g., start_timer) to advise when not to use log_time.

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