jira_log_work

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

No annotations are provided, so the description must carry the full burden. It mentions routing through `/api/tools/invoke` with JWT/tenant/company scope, which is a minor disclosure. However, it does not describe what the operation does (e.g., creates a worklog, updates time spent), permissions required, idempotency, or side effects. The behavioral traits are insufficient for safe invocation.

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 short (3 sentences), which is concise. However, the first sentence is tautological, repeating the name. The second sentence contains routing info that may not be relevant for tool selection. The structure front-loads low-value information and lacks clear, actionable guidance.

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 that this is a Jira time-logging tool with an output schema (present but not detailed), the description lacks key information: what the tool returns, what arguments are required inside the JSON string, and how it relates to other Jira tools. Compared to siblings with more explicit descriptions, this is incomplete.

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%, meaning the schema has no descriptions for the single `arguments` parameter. The description says 'JSON string of arguments' but does not specify the expected structure (e.g., issue key, time spent, comment). This adds minimal value beyond the schema and leaves the agent guessing about valid inputs.

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 states it is a Jira connector operation `log_work`, which is slightly vague. It does not explicitly say 'Log time/work on a Jira issue' in plain language. The name is somewhat descriptive but the description adds little clarity beyond the name itself. It fails to differentiate from sibling tools like jira_add_comment or jira_create_issue.

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?

There is no guidance on when to use this tool versus alternatives. No context about prerequisites (e.g., need a Jira issue key), no exclusions, and no mention of related tools. The description only provides routing details, which are not helpful for usage decisions.

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