gitea_execute

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

With no annotations, the description carries the burden and does well: it discloses the side-effecting nature ('side-effecting actions') and warns about strict validation ('Params validated strictly: unknown keys, wrong types, missing required → ValueError'). It also explains the introspection operations 'help' and 'schema' which let the agent discover behavior. It does not mention permissions or reversibility, but the side-effect warning is a strong disclosure.

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 moderately sized but every line is functional. The intro line defines scope, then bullet-like code lines explain each operation mode. It is well-structured and front-loaded with the core purpose. It could be slightly trimmed, but it is not wasteful.

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 is a generic dispatcher with potentially many operations, the description is fairly complete. It explains the invocation pattern, discovery mechanisms, and validation behavior. It doesn't list all possible ops, but the 'help' operation exists for that. It could mention return values, but the 'schema' operation likely provides that for each op. Overall, it covers the essential usage context well.

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 provides only 'operation' and 'params' with no descriptions, and 0% coverage. The description adds rich semantics: operation selects the op, params holds arguments, and it details special operations ('help', 'schema') with usage examples. This fully compensates for the schema's vagueness.

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.' This gives a specific verb (trigger) and resource (Gitea actions), and explicitly distinguishes it from the CRUD siblings by saying 'beyond plain CRUD'. It also provides concrete examples (merge PRs, dispatch workflows).

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 clearly implies when to use this tool: for side-effecting actions beyond plain CRUD. It also explains discoverability via 'help' and 'schema' operations. However, it does not explicitly name sibling alternatives or state 'use this instead of gitea_write for workflow dispatch'. The boundary is clear but not explicitly exclusionary.

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