gitea_create_milestone

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only indicates a write operation ('Create') but fails to disclose idempotency, side effects, required authentication/authorization levels, rate limits, or what constitutes a successful response.

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 appropriately brief and front-loaded, consisting of a single sentence. However, the '[UNIFIED]' tag is unnecessary metadata that wastes space without adding value to an AI agent.

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 7 parameters with no schema descriptions, no annotations, and no output schema, the description is grossly incomplete. A creation tool of this complexity requires parameter documentation, return value specification, and error handling guidance, none of which are present.

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 zero information about the 7 parameters. No guidance on parameter formats (e.g., due_on date format, valid state strings), validation rules, or semantic relationships between site/owner/repo is provided.

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 identifies the core operation ('Create a new milestone') and target resource ('in a repository'), distinguishing it from sibling tools like gitea_list_milestones or gitea_close_issue. However, the '[UNIFIED]' prefix is noise that slightly obscures the purpose, and it lacks scope constraints (e.g., whether it checks for duplicates).

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 usage guidance is provided. There is no mention of prerequisites (e.g., repository must exist, user needs write permissions), when to use this versus updating an existing milestone, or error conditions (e.g., duplicate title handling).

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