add_work_item

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the mutation/multi-instance profile is covered structurally. The description adds no behavioral context of its own — notably it does not warn that repeat calls are non-idempotent and will create duplicate work items, which is the main behavioral risk for a time-logging 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?

The one-line purpose is front-loaded and each parameter gets exactly one compact line. The Args: block is somewhat template-like and adds no scene-setting, but there is no wasted text.

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?

An output schema exists, so return-value explanation is not required, and all six parameters are addressed. The remaining gap is behavioral (duplicate-entry risk on a non-idempotent mutation), but the description is otherwise adequate to invoke the tool correctly.

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% (only bare titles), so the description carries the full burden and largely succeeds: it documents date format (YYYY-MM-DD) with a default of today, that description is optional, and that work_type accepts a display name or a WorkItemType id. Only 'instance' is left as a bare '(optional)' with no meaning beyond the name.

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 opening line states a specific verb+resource: 'Log time on a YouTrack issue', which is unambiguous and distinct from the sibling read/write operations get_work_items, update_work_item and delete_work_item. It does not name those siblings explicitly, so it stops short of full differentiation.

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 update_work_item or delete_work_item, nor any prerequisite or context note. Logging time implies the use case, but no explicit when/when-not or alternative routing is provided.

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