jira_log_work

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

No annotations are provided, so the description carries the burden. It discloses important behavioral details: accepted time_spent formats, started defaulting to now, and the special 'daily' behavior. However, it does not mention side effects, return values, or error handling, leaving gaps for a mutation tool.

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?

Three sentences with no fluff. It leads with the core action, then clarifies key parameter formats, then the special daily mode. Every sentence earns its place.

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 the moderate complexity and presence of an output schema (not shown but noted as present), the description covers purpose, formats, and special behavior well. It omits permissions or error cases, but for a single-worklog editor, the provided context is sufficient for selection and basic 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 coverage is 100%, but the description adds valuable semantics beyond the schema: concrete examples for time_spent ('2:40', '1h 30m'), explicit 'empty = now' for started, and the special issue_key='daily' meaning. This genuinely helps the agent invoke correctly.

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 opens with a specific verb+resource: 'Logs one worklog.' It clearly distinguishes from sibling jira_log_work_batch by emphasizing 'one', and also describes a special mode for issue_key='daily'. The purpose is unambiguous.

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 implicitly differentiates from jira_log_work_batch by saying 'one worklog', and explains when to use the daily bucket. However, it does not explicitly state when to use this tool versus the batch sibling, so some inference is required.

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