log_time

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

No annotations are provided, and the description is too brief to disclose behavioral traits such as idempotency, permission requirements, side effects (e.g., overwriting existing entries), or what happens on success/failure. The agent gains little insight beyond the action itself.

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 with no wasted words. It is front-loaded and efficient. However, given the tool's complexity (6 parameters), a slightly longer description could improve clarity without sacrificing conciseness.

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 6 parameters, no output schema, and no annotations, the description is inadequate. It does not explain return values, error conditions, or the optional nature of issueId. The tool's behavior remains ambiguous for an AI agent to invoke correctly without additional context.

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 has 100% parameter description coverage, so the schema already documents each parameter. The description adds the context 'manually' but does not explain relationships between parameters (e.g., issueId is optional, projectId is required). Baseline 3 applies since the schema carries the burden.

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 action ('Log') and resource ('time spent on an issue') and adds 'manually' to differentiate from timer-based logging. However, it implies time is always associated with an issue, while issueId is optional; the tool can log time to a project without an issue, making the description slightly imprecise.

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 on when to use this tool versus siblings like start_timer, stop_timer, or list_time_entries. The word 'manually' hints at the distinction, but no explicit when-to-use or when-not-to-use information is provided, leaving the agent to infer context.

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