gitea_execute

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

No annotations are provided, so the description carries full burden. It discloses side-effecting nature, strict validation, and error behavior ('ValueError with field-level detail'). However, it lacks details on authentication requirements or rate limits.

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 well-structured with bullet-like lines and code examples. It is clear but slightly verbose; however, every sentence adds essential value.

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 complexity as a meta-dispatcher, the description covers all modes, usage, validation, and examples. No output schema exists, but return behaviors for help/schema/invoke are adequately described.

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 input schema has 0% description coverage, so the description completely compensates. It explains the 'operation' parameter (help, schema, op names) and 'params' parameter (filtering for help, schema, or invoke arguments). It adds validation rules and usage patterns far beyond the raw schema.

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 states 'Gitea action triggers — merge PRs, dispatch workflows, and other side-effecting actions beyond plain CRUD,' which is a specific verb and resource. It distinguishes from sibling tools that are plain CRUD (gitea_read, gitea_write, gitea_delete, gitea_admin_read/write).

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 explains different operation modes (help, schema, invoke) with examples. It implicitly suggests when to use this tool over siblings, but does not explicitly state when not to use it or provide exclusions.

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