gitea_create_work_item

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

With no annotations, description carries full burden. It mentions 'plan or create' and dry_run default true, but does not disclose mutation behavior, permissions, or what happens on actual creation. Lacks important behavioral context.

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?

Description is a single sentence, concise but lacks any structure or bullet points. It is adequate but could be more informative without being verbose.

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 10 parameters, 0% schema coverage, no annotations, and an output schema that is not described, the tool definition is highly incomplete. The agent would have no understanding of parameter semantics or return values 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?

Schema description coverage is 0% and the description adds no parameter explanations. Among 10 parameters, only title, body, and labels are somewhat guessable; ref, dotenv_path, milestone_id etc. are unexplained. No value added beyond schema titles.

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 the tool creates a Gitea issue work item, using specific verb and resource. However, it doesn't differentiate from siblings like gitea_create_sprint or gitea_list_work_items, and 'work item' is ambiguous (issue vs task).

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 vs alternatives like gitea_create_sprint or other issue creation tools. Description does not mention prerequisites, context, or when not to use.

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