configure_gitea

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

With no annotations provided, the description fully carries the behavioral burden. It discloses session-scoped, never-persisted behavior, token handling (tokens never pass through), strict username filtering, and re-discovery triggers. This is rich, unambiguous behavioral context beyond anything structured.

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 compact yet information-dense. Every sentence earns its place: first sentence states purpose and scope, second lists accepted parameters and requirement, third explains credential sources and re-discovery, fourth addresses token handling, fifth clarifies filtering and usage triggers. Well-structured and front-loaded.

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 the tool's role (configuration) and absence of output schema/annotations, the description covers all essentials: input parameters, minimal requirement, credential flow, identity selection, and usage scenarios. No critical behavioral gaps remain for an agent to invoke it 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?

The schema already covers all four parameters at 100%, giving baseline 3. The description adds meaningful semantics: 'at least one is required', base_url/username trigger re-discovery, and username's exact-match filtering. It enriches the static schema descriptions into actionable behavioral rules.

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 uses a specific verb 'Configure' with a clear resource 'Gitea connection' and explicitly states session scoping and non-persistence. It clearly distinguishes this configuration tool from all sibling tools, which perform issue, repo, or release operations.

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?

The description explicitly states when to use it: 'Use this when the server started unconfigured or when you need to switch instances/identities mid-session.' It also explains the re-discovery trigger conditions, giving clear context for choosing this tool over others.

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