Create GitHub issue

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the issue is created in the linked repository and requires configuration. However, it does not disclose whether the operation is idempotent, any side effects (e.g., notification triggers), or what happens on failure. The absence of such details leaves some behavioral ambiguity.

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 concise with four sentences, front-loaded with the main purpose. Every sentence adds value: purpose, use cases, location, prerequisites. Could be slightly more streamlined, but overall efficient.

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 lack of annotations and output schema, the description should explain what the tool returns (e.g., issue URL or number) or error conditions. It fails to do so, leaving the agent unaware of the tool's output. This gap reduces completeness.

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 coverage is 100%, so the schema already documents the parameters. The description adds no additional meaning beyond stating that labels are optional (already in schema) and that the body supports Markdown (also in schema). Thus, it does not exceed the baseline of 3.

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 the action (creating a GitHub issue) and the resource (project's connected repository). It lists specific use cases (report bugs, track failures, action items) and the verb 'Create' is precise. Although it does not explicitly distinguish from siblings, the sibling tools are all different actions (suite creation, analysis, etc.), so purpose is unambiguous.

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 provides explicit scenarios for use: reporting bugs, tracking test failures, and creating action items from chat discussions. It also mentions prerequisites (GitHub integration configured and WOPEE_PROJECT_UUID set). However, it does not state when not to use the tool or mention alternatives, but given no alternative issue-creation tools exist among siblings, this is minor.

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