Gitea: List milestones

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. Beyond that the description adds nothing: it does not say that results default to open milestones only, whether closed milestones require an explicit state value, or anything about pagination or ordering of results.

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?

A single short sentence with the scope front-loaded and no padding. It is efficient, though "[UNIFIED]" is dead weight and the brevity comes at the cost of any useful detail.

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?

For a simple read-only list tool with no output schema, a one-liner is defensible, and the annotations carry the safety profile. However, with four parameters at 0% schema coverage and a non-obvious state default, the definition leaves gaps an agent must guess at.

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%, so the description has to compensate. "In a repository" loosely maps to owner/repo, but the site parameter and the state filter (defaulting to "open") are left entirely unexplained, so callers cannot infer how to retrieve closed milestones.

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?

"List all milestones in a repository" gives a specific verb (list) plus resource (milestones) and scope (repository), which is enough to separate it from gitea_create_milestone. The gratuitous "[UNIFIED]" prefix adds no discriminating information, and no sibling alternative (e.g. create_milestone) is named as a contrast.

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 when-to-use guidance, no prerequisites, and no mention of alternatives or when not to call it. The only usage-relevant hint buried in the schema is the state default, and the description never surfaces it.

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